Triple
T33735705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lao Skyway |
E864407
|
entity |
| Predicate | servesDestinationCountry |
P104635
|
FINISHED |
| Object | Laos |
—
|
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: Laos | Statement: [Lao Skyway, servesDestinationCountry, Laos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesDestinationCountry Context triple: [Lao Skyway, servesDestinationCountry, Laos]
-
A.
destinationCountryServed
chosen
Indicates that a given entity (such as a service, route, or provider) serves or operates to a specified destination country.
-
B.
servesCountryGroup
Indicates that an entity provides service, support, or functions on behalf of a specified group of countries.
-
C.
hasCountryServed
Indicates that a person or organization has provided service to, or performed duties on behalf of, a specified country.
-
D.
servesDestinationType
Indicates that an entity provides service to, or is intended for use with, a specific type or category of destination.
-
E.
servedDomesticDestination
Indicates that a transportation service (such as an airline or train operator) provided service to a destination located within the same country.
- 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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff6ef0d61c81909162d37c15a1a3c3 |
completed | May 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69ff6c6a58e08190921317062cd9d489 |
completed | May 9, 2026, 5:18 p.m. |
Created at: May 1, 2026, 1:44 a.m.