Triple
T8965135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seafield |
E214110
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Livingston |
E24590
|
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: Livingston | Statement: [Seafield, near, Livingston]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Livingston Context triple: [Seafield, near, Livingston]
-
A.
Livingston
chosen
Livingston is a large post-war new town in West Lothian, Scotland, known as a major residential and commercial centre within the Edinburgh commuter belt.
-
B.
Livingston
Livingston is a prominent American family name historically associated with influential political figures, landowners, and statesmen, particularly in New York.
-
C.
Livingston
Livingston is a residential neighborhood on Staten Island, New York City, known for its historic character and proximity to cultural institutions like Snug Harbor.
-
D.
Livingston
Livingston is a small agricultural city in California’s Central Valley, located in Merced County.
-
E.
Livingston
Livingston is a small Montana city known as a historic railroad town and gateway to Yellowstone National Park, with a vibrant arts scene and scenic mountain surroundings.
- 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_69ca839cd6008190a1546a701a56710c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc674c4be8819090d46aba8ab40af3 |
completed | April 1, 2026, 12:31 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfc95514408190ad442069daec0459 |
completed | April 3, 2026, 2:06 p.m. |
Created at: March 30, 2026, 7:01 p.m.