Triple
T2250543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adam Driver |
E49605
|
entity |
| Predicate | knownFor |
P22
|
FINISHED |
| Object | Paterson |
E19335
|
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: Paterson | Statement: [Adam Driver, knownFor, Paterson]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Paterson Context triple: [Adam Driver, knownFor, Paterson]
-
A.
Paterson
Paterson is an Australian federal electoral division in New South Wales, represented in the national Parliament.
-
B.
Paterson, New Jersey
chosen
Paterson, New Jersey is a historic industrial city in northern New Jersey known for its diverse immigrant communities, including a significant Dutch American presence.
-
C.
Newburgh
Newburgh is a small rural village in Lancashire, England, known for its historic buildings and scenic countryside setting.
-
D.
Newburgh
Newburgh is a small historic town in eastern Scotland known for its scenic setting on the River Tay and its traditional Scottish character.
-
E.
Newark
Newark is a small suburban city in California’s San Francisco Bay Area, located near the southern end of the East Bay.
- 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_69a88aaa9250819095e127d0d77e8a32 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc11b61888190af3b11b87dc8e0dc |
completed | March 7, 2026, 6:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b56b217af0819084d8aed695b8377b |
completed | March 14, 2026, 2:05 p.m. |
Created at: March 4, 2026, 7:47 p.m.