Triple
T26086983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colonel Creighton |
E658009
|
entity |
| Predicate | supervisesInFiction |
P124603
|
FINISHED |
| Object | Kimball O’Hara |
—
|
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: Kimball O’Hara | Statement: [Colonel Creighton, supervisesInFiction, Kimball O’Hara]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supervisesInFiction Context triple: [Colonel Creighton, supervisesInFiction, Kimball O’Hara]
-
A.
responsibleForFictional
Indicates that one entity bears responsibility for creating, managing, or causing a fictional work, character, event, or universe associated with another entity.
-
B.
guardedByInFiction
Indicates that one fictional entity is protected or watched over by another within a narrative context.
-
C.
conductsInFiction
chosen
Indicates that an entity carries out or performs an action or role within a fictional context or narrative.
-
D.
governedByFictional
Indicates that one entity is under the rule, control, or authority of another entity that is fictional or exists only in an imagined context.
-
E.
eraWithinFiction
Indicates that a time period or era exists inside the narrative world or timeline of a fictional work.
- 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_69ee5bbf0d208190801ee95d4f07fb16 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 26, 2026, 7:43 p.m.