Triple
T23452681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Jersey Route 156 |
E567826
|
entity |
| Predicate | formerAlignmentOf |
P46340
|
FINISHED |
| Object | U.S. Route 130 |
—
|
NE NERFINISHED |
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: U.S. Route 130 | Statement: [New Jersey Route 156, formerAlignmentOf, U.S. Route 130]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerAlignmentOf Context triple: [New Jersey Route 156, formerAlignmentOf, U.S. Route 130]
-
A.
originallyAlignedWith
Indicates that an entity was initially in agreement, support, or association with another entity or group, regardless of any later changes in stance or affiliation.
-
B.
previousAlignment
Indicates that one entity’s alignment or orientation occurred earlier in time than another’s.
-
C.
eraAlignment
Indicates that two entities are associated with, or correspond to, the same historical or temporal era.
-
D.
realignedFrom
chosen
Indicates that something has been adjusted or repositioned from a previous alignment, configuration, or orientation to a new one.
-
E.
successorAlignment
Indicates that one entity’s alignment, orientation, or configuration directly follows and is determined by that of another entity in a sequence or progression.
- F. None of above.
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_69e2458b4c888190b1d7998f9862a558 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a694f19081909117bc9b10ca8a83 |
completed | April 29, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:52 p.m.