Triple
T35009157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lionheart: Legacy of the Crusader |
E1009899
|
entity |
| Predicate | hasCharacterCreation |
P197997
|
FINISHED |
| Object | customizable protagonist |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: customizable protagonist | Statement: [Lionheart: Legacy of the Crusader, hasCharacterCreation, customizable protagonist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCharacterCreation Context triple: [Lionheart: Legacy of the Crusader, hasCharacterCreation, customizable protagonist]
-
A.
hasCreatedCharacterFor
Indicates that one entity has created or designed a character specifically for another entity or context.
-
B.
characterCreator
Indicates that one entity is the creator or originator of a character associated with another entity.
-
C.
hasCharacterCreatedUnderName
Indicates that one entity has created a character that is associated with or published under a particular name.
-
D.
hasCreation
Indicates a relationship where one entity is the creator or originator of another entity.
-
E.
hasPrimaryCharacter
Indicates that an entity features another entity as its main or central character.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76dcb716881909f75e4fd60ab2284 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fec00f27988190955de6b6348a4d97 |
completed | May 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69febd52037c8190b475dbd50fdbc13e |
completed | May 9, 2026, 4:51 a.m. |
| PDg | Predicate description generation | batch_69fec00e5c1c819083d174bb4bc35f29 |
completed | May 9, 2026, 5:03 a.m. |
Created at: May 3, 2026, 4:01 p.m.