Triple
T7462452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Companion Pass |
E176283
|
entity |
| Predicate | requiresSameFlights |
P77251
|
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: [Companion Pass, requiresSameFlights, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresSameFlights Context triple: [Companion Pass, requiresSameFlights, true]
-
A.
associatedWithFlight
Indicates a relationship where an entity is linked or connected to a specific flight, such as by participation, operation, or relevance.
-
B.
numberOfFlights
Indicates the total count of flights associated with a given entity or within a specified context.
-
C.
hasScheduledFlights
Indicates that there are one or more flights planned and set to occur between the related entities according to a schedule.
-
D.
originatingFlight
Indicates that one entity is the original or initial flight from which another flight, journey, or related record derives or is associated.
-
E.
performedFlightTo
Indicates that an entity (such as an aircraft or airline) carried out a flight whose destination was a specified location.
- 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_69c69f21632481908bf83f6c6da897e3 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3d80ae08190ba383066cf0cb2ce |
completed | March 27, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c6f03bad9c8190bdd5abb86d37df47 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f386daac81908ded91b397b44148 |
completed | March 27, 2026, 9:15 p.m. |
Created at: March 27, 2026, 3:39 p.m.