Triple
T24223639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Golden Age |
E601528
|
entity |
| Predicate | hasNotableProtagonist |
P63978
|
FINISHED |
| Object | Steve Redgrave |
—
|
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: Steve Redgrave | Statement: [A Golden Age, hasNotableProtagonist, Steve Redgrave]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableProtagonist Context triple: [A Golden Age, hasNotableProtagonist, Steve Redgrave]
-
A.
hasNoHumanProtagonist
Indicates that in the described work or narrative, none of the main protagonists are human characters.
-
B.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
C.
hasNotableHero
chosen
Indicates that an entity is associated with a particularly distinguished or prominent hero.
-
D.
doesNotFeatureCharacterDirectly
Indicates that the subject work does not include the specified character as an on-screen, on-page, or otherwise directly appearing participant in its content.
-
E.
hasHumanProtagonists
Indicates that the primary characters driving the narrative are human beings rather than non-human entities.
- 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_69e29537ca548190b94a37ebe1977caf |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f287dd148081909f02e521ad6043b1 |
completed | April 29, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, midnight