Triple
T20511601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dana Holding Corporation |
E503577
|
entity |
| Predicate | hasBrand |
P1500
|
FINISHED |
| Object | Spicer |
—
|
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: Spicer | Statement: [Dana Holding Corporation, hasBrand, Spicer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Spicer Context triple: [Dana Holding Corporation, hasBrand, Spicer]
-
A.
Spicer
chosen
Spicer is a surname of English origin borne by various notable individuals across different fields.
-
B.
Spiner
Spiner is the surname of American actor Brent Spiner, best known for portraying the android Data in the Star Trek franchise.
-
C.
Klepper
Klepper is the surname of American comedian and television host Jordan Klepper, known for his work on political satire programs such as The Daily Show.
-
D.
Gillespie
Gillespie is a Scottish-origin surname most famously associated with American jazz trumpeter and composer Dizzy Gillespie.
-
E.
Spiro
Spiro is a masculine given name most notably borne by Spiro Agnew, the 39th vice president of the United States.
- 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_69e0b4b2aa788190ae9eb37c1d73b1f1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69dcb8f5c8190b0d4c09f3669a8ec |
completed | April 20, 2026, 9:42 p.m. |
Created at: April 16, 2026, 11:36 a.m.