Triple
T9505745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manila–New York |
E229263
|
entity |
| Predicate | isNonSchengenRoute |
P33077
|
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: [Manila–New York, isNonSchengenRoute, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNonSchengenRoute Context triple: [Manila–New York, isNonSchengenRoute, true]
-
A.
supportsNonSchengenFlights
chosen
Indicates that the subject facility or service is capable of handling or accommodating flights that operate outside the Schengen Area.
-
B.
supportsSchengenFlights
Indicates that an entity enables or accommodates flights operating within the Schengen Area.
-
C.
hasSchengenArea
Indicates that a place, country, or region is part of, or included within, the Schengen Area for border-free movement.
-
D.
hasEuropeanRoute
Indicates that a road or segment is designated as part of a specific European route within the trans-European road network.
-
E.
passesThroughCountry
Indicates that a route, path, or object traverses or crosses within the boundaries of a specified 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_69ca847611c48190a28c028644198c75 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9852b7e48190a8f69cbde10d2858 |
completed | April 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cca567ca448190bf4bcce8ce7dd54f |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:57 p.m.