Triple
T16269617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bob Dalton |
E394964
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Dalton |
E212418
|
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: Dalton | Statement: [Bob Dalton, familyName, Dalton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dalton Context triple: [Bob Dalton, familyName, Dalton]
-
A.
Dalton
Dalton is a small town in western Massachusetts known historically for its paper mills and as the longtime home of the Crane & Co. currency paper company.
-
B.
Dalton
Dalton is a city in northwest Georgia known for its large carpet and flooring industry, often referred to as the "Carpet Capital of the World."
-
C.
Dalton
chosen
Dalton is a common English surname of Anglo-Saxon origin, historically associated with various notable figures in British public life.
-
D.
Dalton
Dalton is a small borough in northeastern Pennsylvania, located within the suburban and rural region of Lackawanna County near Scranton.
-
E.
Dalton
Dalton is a small rural village in the West Lancashire district of Lancashire, England.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24608dd20819082f46a64af233038 |
completed | April 17, 2026, 2:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0017bceb3881909dbd3167820ef199 |
completed | May 10, 2026, 5:29 a.m. |
Created at: April 10, 2026, 5:05 a.m.