Triple
T31004109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Cup match vs Red Star Belgrade |
E790017
|
entity |
| Predicate | returnJourneyBy |
P180811
|
FINISHED |
| Object | British European Airways Flight 609 |
—
|
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: British European Airways Flight 609 | Statement: [European Cup match vs Red Star Belgrade, returnJourneyBy, British European Airways Flight 609]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnJourneyBy Context triple: [European Cup match vs Red Star Belgrade, returnJourneyBy, British European Airways Flight 609]
-
A.
journeyFrom
Indicates that an entity undertakes or originates a journey starting from a specified location or source.
-
B.
journeyFunction
Indicates a relationship where an entity serves as the purpose, role, or functional objective of a journey or travel event.
-
C.
returnJourneyLength
Indicates the total distance or duration of a journey back from a destination to its point of origin.
-
D.
journeyDestination
Indicates that one entity serves as the endpoint or intended destination of another entity’s journey or travel.
-
E.
dateOfJourney
Indicates the specific calendar date on which a particular journey or trip takes place.
- 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
| PDg | Predicate description generation | batch_69f7516c538481908c6e55cf76add098 |
completed | May 3, 2026, 1:45 p.m. |
Created at: April 29, 2026, 8:57 p.m.