Triple
T18186464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Carter Family |
E435427
|
entity |
| Predicate | notableWork |
P4
|
FINISHED |
| Object | Engine 143 |
—
|
NE NERFINISHED |
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: Engine 143 | Statement: [The Carter Family, notableWork, Engine 143]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Engine 143 Context triple: [The Carter Family, notableWork, Engine 143]
-
A.
Engine 143
chosen
"Engine 143" is a traditional American folk ballad, famously recorded by artists such as Joan Baez, that tells the tragic story of a doomed train and its engineer.
-
B.
Engine 163
Engine 163 is a New York City Fire Department engine company serving Staten Island as part of FDNY’s network of frontline firefighting units.
-
C.
Engine 165
Engine 165 is a New York City Fire Department engine company serving the New Dorp neighborhood on Staten Island.
-
D.
Tiger Engine
Tiger Engine is Bungie's proprietary game engine best known for powering the Destiny series of online first-person shooters.
-
E.
Oh! Mighty Engine
Oh! Mighty Engine is a 2008 solo album by British singer-songwriter Neil Halstead, known for its gentle, introspective folk sound and understated acoustic arrangements.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dffe9e8081909c6bff40bbd279d2 |
completed | April 19, 2026, 2 p.m. |
Created at: April 10, 2026, 10:31 a.m.