Triple
T27285340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 790 (New York) |
E688455
|
entity |
| Predicate | isSignedConcurrentWith |
P162305
|
FINISHED |
| Object | New York State Route 5 |
—
|
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: New York State Route 5 | Statement: [Interstate 790 (New York), isSignedConcurrentWith, New York State Route 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSignedConcurrentWith Context triple: [Interstate 790 (New York), isSignedConcurrentWith, New York State Route 5]
-
A.
alsoSignedWith
Indicates that an entity signed or endorsed something together with another specified entity, as part of the same signing action or agreement.
-
B.
isSignedAlong
Indicates that an entity has signed or endorsed something in conjunction with another specified entity.
-
C.
isSigned
Indicates that an entity has been formally endorsed or authenticated through a signature or signing action.
-
D.
coSignedWith
Indicates that an entity has jointly signed a document, agreement, or obligation together with another entity.
-
E.
mayBeSignedAs
Indicates that one entity can optionally be used or recognized as the signature or signed form of another entity.
- F. None of above. chosen
Provenance (4 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_69ef355998e08190bdff849e8f33adce |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6275567608190a38a798ecbc1d99d |
completed | May 2, 2026, 4:33 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f622a8fe7c819096e8a43db263a423 |
completed | May 2, 2026, 4:13 p.m. |
Created at: April 27, 2026, 11:11 a.m.