Triple
T10378398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princeton |
E244565
|
entity |
| Predicate | hasNearbyCity |
P350
|
FINISHED |
| Object | Trenton |
E36449
|
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: Trenton | Statement: [Princeton, hasNearbyCity, Trenton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Trenton Context triple: [Princeton, hasNearbyCity, Trenton]
-
A.
Trenton
Trenton is a community in Ontario, Canada, located at the eastern end of the Trent–Severn Waterway and known as a regional hub on the Bay of Quinte.
-
B.
Trenton
Trenton is a small city in Gilchrist County, Florida, serving as a local hub for surrounding rural communities.
-
C.
Trenton, New Jersey
chosen
Trenton, New Jersey is the capital city of the state of New Jersey, located along the Delaware River between New York City and Philadelphia.
-
D.
Trenton–Camden
Trenton–Camden is a key urban corridor in New Jersey linking the state capital of Trenton with the city of Camden along the Delaware River.
-
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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e98fead88190ace49f34b8a27c25 |
completed | April 7, 2026, 11:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d9987838ac8190a6ba09305fc27621 |
completed | April 11, 2026, 12:40 a.m. |
Created at: April 6, 2026, 12:03 p.m.