Triple
T37006513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 495 (former) in New Jersey |
E915816
|
entity |
| Predicate | currentNumbering |
P134912
|
FINISHED |
| Object | Route 495 (New Jersey) |
—
|
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: Route 495 (New Jersey) | Statement: [Interstate 495 (former) in New Jersey, currentNumbering, Route 495 (New Jersey)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentNumbering Context triple: [Interstate 495 (former) in New Jersey, currentNumbering, Route 495 (New Jersey)]
-
A.
numberingStatus
Indicates the status or condition of an entity’s assigned number or numbering process (e.g., whether it has been numbered, is pending, or has a particular numbering state).
-
B.
numberingType
Indicates the scheme or style used to assign sequential numbers or labels within an ordered set.
-
C.
followsNumbering
chosen
Indicates that one entity adheres to or continues the numbering sequence established by another entity.
-
D.
numberingRole
Indicates a role or function that an entity plays in a numbering or sequencing system.
-
E.
numberingReason
Indicates the rationale or basis for assigning a particular number or numbering scheme to something.
- 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_69f76e90ed548190b187d2475f5c807d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff9e91bba08190af04b31ad815b13a |
completed | May 9, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69ff9e00e4808190bde8f07e6519a72c |
completed | May 9, 2026, 8:50 p.m. |
Created at: May 3, 2026, 4:14 p.m.