Triple
T36361508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terrence "Scooter" Williams |
E895504
|
entity |
| Predicate | hasPrimaryStorylineWith |
P204841
|
FINISHED |
| Object | Khadijah James |
E1109741
|
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: Khadijah James | Statement: [Terrence "Scooter" Williams, hasPrimaryStorylineWith, Khadijah James]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryStorylineWith Context triple: [Terrence "Scooter" Williams, hasPrimaryStorylineWith, Khadijah James]
-
A.
hasPrimaryStory
Indicates that one entity is designated as the main or most important story associated with another entity.
-
B.
hasStorylineType
Indicates that an entity’s storyline belongs to or is categorized under a specific type or narrative classification.
-
C.
hasNarrativeArcOf
Indicates that one entity embodies, represents, or corresponds to the narrative arc (story progression or plot structure) of another entity.
-
D.
hasNarrativeArcIn
Indicates that an entity’s storyline or narrative progression occurs within or is contained by a specified work, context, or medium.
-
E.
hasMainPlotElement
Indicates that one entity serves as a central or primary plot element within the narrative of another entity.
- F. None of above. chosen
Provenance (5 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_69f76e5044248190b390d8887dc03254 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39dbbc4f9081909f83c4fc506083cf |
completed | June 23, 2026, 1:05 a.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:09 p.m.