Triple
T27395035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 192 |
E691654
|
entity |
| Predicate | alsoSignedAs |
P159997
|
FINISHED |
| Object | State Road 530 |
—
|
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: State Road 530 | Statement: [U.S. Route 192, alsoSignedAs, State Road 530]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoSignedAs Context triple: [U.S. Route 192, alsoSignedAs, State Road 530]
-
A.
alsoSignedAs
chosen
Indicates that an entity is additionally known to have signed or endorsed something under another name or identity.
-
B.
alsoSignedWith
Indicates that an entity signed or endorsed something together with another specified entity, as part of the same signing action or agreement.
-
C.
isAlsoSignedAs
Indicates that an entity is known or recorded under an additional signature, alias, or signing name besides its primary one.
-
D.
signedAs
Indicates that an entity has signed or endorsed something using a particular name, role, or identity.
-
E.
coSignedWith
Indicates that an entity has jointly signed a document, agreement, or obligation together with another entity.
- 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_69ef5204f7048190bf226a129858fc5b |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62cafdb208190b2824c05412669af |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:27 p.m.