Triple
T19599104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Incheon International Airport Expressway |
E470420
|
entity |
| Predicate | hasSpeedLimitKmPerHour |
P2129
|
FINISHED |
| Object | 100 |
—
|
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: 100 | Statement: [Incheon International Airport Expressway, hasSpeedLimitKmPerHour, 100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpeedLimitKmPerHour Context triple: [Incheon International Airport Expressway, hasSpeedLimitKmPerHour, 100]
-
A.
hasSpeedLimit
chosen
Indicates that a specified maximum allowable speed is imposed on the associated entity or context.
-
B.
hasSpeedLimitCharacteristic
Indicates that an entity is associated with a specific speed limit property or constraint.
-
C.
hasSpeedLimitRange
Indicates that there is a specified minimum and maximum speed limit applicable to a given context or segment.
-
D.
hasSpeedRestriction
Indicates that an entity is subject to a specified limit on its allowable speed.
-
E.
speedLimitCharacteristic
Indicates that an entity has a specific speed limit property or constraint associated with it.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6407d46188190b9818665b2a698a5 |
completed | April 20, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69e514e166dc8190a0f147e0b4c8bbe7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.