Triple
T37933515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Farm to Market Road 922 |
E946280
|
entity |
| Predicate | speedEnvironment |
P47160
|
FINISHED |
| Object | rural speed limits |
—
|
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: rural speed limits | Statement: [Farm to Market Road 922, speedEnvironment, rural speed limits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speedEnvironment Context triple: [Farm to Market Road 922, speedEnvironment, rural speed limits]
-
A.
roadEnvironment
chosen
Indicates that the relationship or action occurs within, is influenced by, or is specifically associated with a road or roadway environment.
-
B.
speedDependsOn
Indicates that the speed of one entity is determined or influenced by another specified factor or entity.
-
C.
speedDescribedAs
Indicates that one entity characterizes or labels the speed of another entity using a particular description or term.
-
D.
speedSupervision
Indicates a relationship where an entity monitors, controls, or enforces limits on the speed of another entity or process.
-
E.
speed
Indicates the rate at which an entity moves or changes position over time.
- 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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.