Triple
T4779114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Falls Historic District |
E106128
|
entity |
| Predicate | city |
P40
|
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: [Great Falls Historic District, city, Paterson]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Paterson Context triple: [Great Falls Historic District, city, Paterson]
-
A.
Paterson
Paterson is an Australian federal electoral division in New South Wales, represented in the national Parliament.
-
B.
Paterson
Paterson is a Scottish-origin surname borne by various notable individuals across politics, law, sports, and the arts.
-
C.
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.
-
D.
Newburgh
Newburgh is a small rural village in Lancashire, England, known for its historic buildings and scenic countryside setting.
-
E.
Newburgh
Newburgh is a small historic town in eastern Scotland known for its scenic setting on the River Tay and its traditional Scottish character.
- 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_69bd43f3074c8190937e7b0a457fe9f1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd658942e481908570cfec77fe4a4b |
completed | March 20, 2026, 3:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0e2efb6d4819091ed08faec3b6c4a |
completed | March 23, 2026, 6:51 a.m. |
Created at: March 20, 2026, 1:21 p.m.