Triple
T37553416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gromgol Base Camp |
E933640
|
entity |
| Predicate | hasFlightPathTo |
P105188
|
FINISHED |
| Object | Booty Bay |
—
|
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: Booty Bay | Statement: [Gromgol Base Camp, hasFlightPathTo, Booty Bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFlightPathTo Context triple: [Gromgol Base Camp, hasFlightPathTo, Booty Bay]
-
A.
hasAirTravelLink
chosen
Indicates that there is a direct or established air travel connection (such as flights or air routes) between the related entities.
-
B.
flightRoute
Indicates a path or sequence of locations that a particular flight travels between, typically from its origin to its destination (and possibly via intermediate stops).
-
C.
hasTaxiway
Indicates that an airport or runway is connected to or served by a taxiway used for aircraft ground movement.
-
D.
hasDepartureTo
Indicates that a departure event originates from one place and is directed toward a specific destination.
-
E.
isFlownOn
Indicates that an entity (such as a person or object) travels or is transported using a particular aircraft or airline as the means of flight.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:17 p.m.