Triple
T36965451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Sunderland |
E914415
|
entity |
| Predicate | endingDependentOn |
P19751
|
FINISHED |
| Object | player choices |
—
|
LITERAL 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: player choices | Statement: [James Sunderland, endingDependentOn, player choices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endingDependentOn Context triple: [James Sunderland, endingDependentOn, player choices]
-
A.
statusDependsOn
Indicates that the status or state of one entity is determined or influenced by the status or state of another entity.
-
B.
endedDueTo
Indicates that an event, process, or state came to a conclusion specifically because of a particular cause or condition.
-
C.
endsOn
Indicates that one entity terminates or concludes precisely at the boundary or endpoint of another entity.
-
D.
dependency
Indicates that one entity relies on, is conditioned by, or cannot function or exist properly without another entity.
-
E.
contingentOn
chosen
Indicates that the occurrence, validity, or outcome of one event or condition depends on the fulfillment or existence of another.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.