Triple
T21743468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Newman as Eddie Felson |
E536723
|
entity |
| Predicate | setInNarrativeContext |
P9801
|
FINISHED |
| Object | American pool halls |
—
|
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: American pool halls | Statement: [Paul Newman as Eddie Felson, setInNarrativeContext, American pool halls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setInNarrativeContext Context triple: [Paul Newman as Eddie Felson, setInNarrativeContext, American pool halls]
-
A.
useInNarrative
Indicates that something is employed as an element or device within a narrative or story.
-
B.
replacesInNarrative
Indicates that one narrative element takes the place of another within the structure or progression of a story.
-
C.
hasPartInNarrative
Indicates that one entity plays a role or participates as a component within the storyline or structure of another narrative entity.
-
D.
hasTypeInNarrative
Indicates that an entity is assigned a specific type or role within the context of a particular narrative.
-
E.
locationOfNarrative
chosen
Indicates the place or setting where the events or story described in the narrative occur.
- 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_69e0c46df5448190b4322127ffc4c690 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01a74592c8190959af631d72df479 |
completed | April 28, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:49 p.m.