Triple
T11758175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR 180 |
E279582
|
entity |
| Predicate | usedInDocumentation |
P38828
|
FINISHED |
| Object | state transportation planning documents |
—
|
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: state transportation planning documents | Statement: [SR 180, usedInDocumentation, state transportation planning documents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInDocumentation Context triple: [SR 180, usedInDocumentation, state transportation planning documents]
-
A.
usedInType
Indicates that something serves as a component, element, or example within a particular type or category.
-
B.
documentedUsing
chosen
Indicates that something is recorded, described, or specified by means of a particular document, tool, or documentation method.
-
C.
usedInMethod
Indicates that something (such as a component, variable, or resource) is utilized or referenced within the execution or implementation of a particular method.
-
D.
usedInLibrary
Indicates that something is utilized or applied within the context of a library, such as a software library or a physical library system.
-
E.
usedInAPIs
Indicates that something is employed or referenced as a component or feature within one or more APIs.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a5220f148190ae60d1941a579ab6 |
completed | April 10, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69d88a829fe481909cc5431de7d6058e |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.