Triple
T25976074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Road |
E645942
|
entity |
| Predicate | mayBeSignedWith |
P90438
|
FINISHED |
| Object | standardized route shields |
—
|
LITERAL 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: standardized route shields | Statement: [State Road, mayBeSignedWith, standardized route shields]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeSignedWith Context triple: [State Road, mayBeSignedWith, standardized route shields]
-
A.
mayBeSignedAs
chosen
Indicates that one entity can optionally be used or recognized as the signature or signed form of another entity.
-
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.
typicallySignedWith
Indicates that an entity is most commonly or customarily accompanied by a particular signature, mark, or signing method.
-
D.
isSigned
Indicates that an entity has been formally endorsed or authenticated through a signature or signing action.
-
E.
requiresSignatureOf
Indicates that one entity must obtain or depend on the formal signature or signed approval of 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_69e77e8768648190b27bb578f14bcb88 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 22, 2026, 8:51 a.m.