Triple
T28469881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Route (South Korea) |
E720404
|
entity |
| Predicate | typicalSpeedLimitHigherThan |
P106467
|
FINISHED |
| Object | Local roads (South Korea) |
—
|
NE NERFINISHED |
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: Local roads (South Korea) | Statement: [National Route (South Korea), typicalSpeedLimitHigherThan, Local roads (South Korea)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSpeedLimitHigherThan Context triple: [National Route (South Korea), typicalSpeedLimitHigherThan, Local roads (South Korea)]
-
A.
typicalSpeedLimitComparedToMainline
chosen
Indicates how the typical speed limit on one road segment compares to that of the mainline or primary roadway.
-
B.
hasSpeedLimit
Indicates that a specified maximum allowable speed is imposed on the associated entity or context.
-
C.
hasSpeedRestriction
Indicates that an entity is subject to a specified limit on its allowable speed.
-
D.
hasSpeedLimitRange
Indicates that there is a specified minimum and maximum speed limit applicable to a given context or segment.
-
E.
regulatesSpeedLimitBy
Indicates that one entity determines, controls, or sets the speed limit applicable to another entity or context.
- 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_69f01a58a67c819097936d9e8da8d6e6 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_6a00ac5654a0819090701f61a5802d64 |
completed | May 10, 2026, 4:03 p.m. |
| PD | Predicate disambiguation | batch_6a00ab94b5e881909e15d1342e5f43be |
completed | May 10, 2026, 4 p.m. |
Created at: April 28, 2026, 2:47 a.m.