Triple
T11095640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enchanted Airways (Singapore version planning phase) |
E262369
|
entity |
| Predicate | indoorOrOutdoorPlanned |
P8552
|
FINISHED |
| Object | outdoor |
—
|
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: outdoor | Statement: [Enchanted Airways (Singapore version planning phase), indoorOrOutdoorPlanned, outdoor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indoorOrOutdoorPlanned Context triple: [Enchanted Airways (Singapore version planning phase), indoorOrOutdoorPlanned, outdoor]
-
A.
indoorOrOutdoor
chosen
Indicates whether an activity, event, or entity occurs inside a building (indoors) or outside in open air (outdoors).
-
B.
hasIndoorType
Indicates that an entity is associated with a specific type or category of indoor environment or indoor feature.
-
C.
isOutdoor
Indicates that an entity or activity takes place outside, in an open-air or non-enclosed environment.
-
D.
outdoorVenue
Indicates that an event, activity, or gathering takes place at a location situated outdoors rather than inside a building or enclosed structure.
-
E.
hasIndoorProgram
Indicates that an entity offers or includes an organized program or activity that takes place indoors.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a0897188190b6c293b44990b3d4 |
completed | April 9, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_69d7441aa3548190b92dbde57841c135 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.