Triple
T6594608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hokkaido Air System |
E148443
|
entity |
| Predicate | notableRouteCharacteristic |
P10970
|
FINISHED |
| Object | short-haul routes |
—
|
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: short-haul routes | Statement: [Hokkaido Air System, notableRouteCharacteristic, short-haul routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRouteCharacteristic Context triple: [Hokkaido Air System, notableRouteCharacteristic, short-haul routes]
-
A.
notableRouteFeature
chosen
Indicates that a route is associated with a distinctive or significant feature, such as a landmark, characteristic terrain, or other notable aspect along its path.
-
B.
notableRouteType
Indicates that a route is particularly significant or well-known for a specific type or category (e.g., scenic, historic, commercial).
-
C.
routeNetworkCharacteristic
Indicates a relationship where a specific characteristic or property is attributed to a route within a network.
-
D.
notableLocationFeature
Indicates that a location is characterized or distinguished by a particular notable physical or contextual feature.
-
E.
notableFeatureOn
Indicates that one entity is a prominent or distinguishing feature located on or part of another entity.
- 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_69c687e7b8688190811ffee72e096468 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6acfd17388190bd0bb8b2371e7df1 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:55 p.m.