Triple
T7731829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iowa Highway 163 |
E175276
|
entity |
| Predicate | signingStandard |
P78412
|
FINISHED |
| Object | Iowa state highway shield |
—
|
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: Iowa state highway shield | Statement: [Iowa Highway 163, signingStandard, Iowa state highway shield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signingStandard Context triple: [Iowa Highway 163, signingStandard, Iowa state highway shield]
-
A.
signingConvention
Indicates that one party formally agrees to and adopts the terms of a convention, treaty, or formal agreement.
-
B.
signatureType
Indicates the specific kind or category of a signature associated with an entity or action.
-
C.
signatureStyle
Indicates the characteristic way in which an entity typically signs its name or marks documents, distinguishing its unique signing pattern or format.
-
D.
signText
Indicates that a sign bears or displays a particular textual content.
-
E.
signatoryType
Indicates the specific role or category of a party that has signed or formally agreed to a document, contract, or agreement.
- 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_69c6995e912c81909a49a2657103f786 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c7016c4a748190a7012030edaefcee |
completed | March 27, 2026, 10:15 p.m. |
| PDg | Predicate description generation | batch_69c7040091608190a9e46ecfb2ff0bca |
completed | March 27, 2026, 10:26 p.m. |
Created at: March 27, 2026, 4:06 p.m.