Triple
T11746797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seoul–Singapore |
E279299
|
entity |
| Predicate | isMajorBusinessRoute |
P101129
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Seoul–Singapore, isMajorBusinessRoute, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorBusinessRoute Context triple: [Seoul–Singapore, isMajorBusinessRoute, true]
-
A.
isBusinessRoute
Indicates that a route functions primarily for business-related travel or commercial purposes between locations.
-
B.
hasMajorRouteType
Indicates that an entity is associated with a primary classification of transportation route (such as highway, rail line, or other major route type).
-
C.
isMajorRoadIn
Indicates that a road is classified as a major road within a specified geographic area or jurisdiction.
-
D.
isMajorRouteInSystem
Indicates that a route functions as a primary or significant corridor within a specified transportation or network system.
-
E.
hasBusinessRoute
Indicates that there exists an established commercial or service route connecting two business-related entities.
- F. None of above. chosen
Provenance (4 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_69d8a50763a081908597da118bd0a64e |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a813cc48190a3dfdc60e8af80ae |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d890458d948190b15054c9ba0fd923 |
completed | April 10, 2026, 5:53 a.m. |
Created at: April 8, 2026, 9:41 p.m.