Triple
T31352287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TGS |
E799629
|
entity |
| Predicate | notablePageInUniverse |
P126931
|
FINISHED |
| Object | Kenneth Parcell |
E248651
|
NE 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: Kenneth Parcell | Statement: [TGS, notablePageInUniverse, Kenneth Parcell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePageInUniverse Context triple: [TGS, notablePageInUniverse, Kenneth Parcell]
-
A.
notedForInUniverse
Indicates that an entity is recognized or distinguished for a particular trait, role, or achievement within a specific fictional universe or narrative continuity.
-
B.
hasInUniverseSignificance
chosen
Indicates that something holds notable importance, relevance, or impact within a particular fictional or conceptual universe.
-
C.
notableWorld
Indicates that an entity is notably recognized or significant on a global or worldwide scale.
-
D.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
E.
notableGiant
Indicates that an entity is recognized as a giant of particular note, standing out for its exceptional size, influence, or significance relative to others of its kind.
- F. None of above.
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_69f224e5e9bc8190a16339328897c4f8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b07621b388190bb5068fa7bb264e8 |
completed | June 11, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:17 p.m.