Triple
T2430976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington State Routes |
E52842
|
entity |
| Predicate | signText |
P39156
|
FINISHED |
| Object | SR route number |
—
|
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: SR route number | Statement: [Washington State Routes, signText, SR route number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signText Context triple: [Washington State Routes, signText, SR route number]
-
A.
signature
Indicates that one entity has provided an official or personal signed endorsement, authorization, or acknowledgment on or for another entity.
-
B.
signatureWork
Indicates that the work is a defining or most representative creation associated with an entity (such as a person, group, or organization).
-
C.
signatureEvent
Indicates an event in which an entity formally signs or authorizes something, such as a document, agreement, or record.
-
D.
signatureLine
Indicates that an entity serves as a designated place or line where a signature is written or recorded.
-
E.
signedAs
Indicates that an entity has signed or endorsed something using a particular name, role, or identity.
- 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_69ab4959bcc0819083246f9fb10439e3 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcc74a5108190a3a9631b0cc1a127 |
completed | March 7, 2026, 6:57 a.m. |
| PD | Predicate disambiguation | batch_69abc5aa1b60819081b87f7985c6cff3 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abcc73d2e48190b6ad5f3ee75b74eb |
completed | March 7, 2026, 6:57 a.m. |
Created at: March 6, 2026, 9:43 p.m.