Triple
T23769536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Black Stallion and Flame |
E587485
|
entity |
| Predicate | hasProtagonistHorse |
P151807
|
FINISHED |
| Object | the Black Stallion |
—
|
NE NERFINISHED |
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: the Black Stallion | Statement: [The Black Stallion and Flame, hasProtagonistHorse, the Black Stallion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtagonistHorse Context triple: [The Black Stallion and Flame, hasProtagonistHorse, the Black Stallion]
-
A.
protagonistHorse
chosen
Indicates that the subject is the main or central horse character in a narrative or story.
-
B.
hasRacehorseCharacter
Indicates that one entity possesses the traits, qualities, or behavioral characteristics associated with a racehorse in relation to another entity or context.
-
C.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
D.
hasNotableHorse
Indicates that an entity is associated with a horse that is considered notable or distinguished in some recognized way.
-
E.
usesHorseType
Indicates that one entity employs, relies on, or operates using a specific type or category of horse.
- F. None of above.
Provenance (3 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_69e2490b8ac48190a6b35f1d5500486b |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c46507708190b0beba7f2b4d0bca |
completed | April 29, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:15 p.m.