Triple
T33121486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drive Shaft |
E847612
|
entity |
| Predicate | originCityInStory |
P86009
|
FINISHED |
| Object | Manchester |
E114
|
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: Manchester | Statement: [Drive Shaft, originCityInStory, Manchester]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originCityInStory Context triple: [Drive Shaft, originCityInStory, Manchester]
-
A.
homeCityInStory
Indicates that a specified city serves as a character’s home city within the context of a particular story.
-
B.
homeCityInBackstory
Indicates that an entity has a specified city as its home city within its narrative or character backstory.
-
C.
cityOfFictionalOrigin
chosen
Indicates the city from which a fictional character, entity, or work is described as originating within its narrative or fictional universe.
-
D.
cityOfOriginal
Indicates the city from which something or someone originally comes or was first created or established.
-
E.
hasOriginStoryLocation
Indicates that an entity’s origin story takes place at or is associated with a specific location.
- 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_69f349588f088190b7c9588860f72033 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a022348ae2881908eae1be79b6f6ff6 |
completed | May 11, 2026, 6:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3525b22cac8190a083878d25e442f2 |
completed | June 19, 2026, 11:19 a.m. |
| PD | Predicate disambiguation | batch_6a0220beb6b08190981fb86363757517 |
completed | May 11, 2026, 6:32 p.m. |
Created at: May 1, 2026, 1:27 a.m.