Triple
T33368179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lod Airport massacre |
E854413
|
entity |
| Predicate | airportRenamed |
P153759
|
FINISHED |
| Object | Ben Gurion Airport |
—
|
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: Ben Gurion Airport | Statement: [Lod Airport massacre, airportRenamed, Ben Gurion Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airportRenamed Context triple: [Lod Airport massacre, airportRenamed, Ben Gurion Airport]
-
A.
airportNameChangedTo
chosen
Indicates that an airport’s official name has been changed from a previous name to a new specified name.
-
B.
renamedToFresnoYosemiteInternationalAirport
Indicates that an entity has undergone a name change to "Fresno Yosemite International Airport."
-
C.
airportLinkReplaced
Indicates that one airport rail or transit link has been superseded or taken over in function by another link.
-
D.
replacedAsMainAirportFor
Indicates that one airport has taken over the role of being the primary or main airport serving a particular area from another airport.
-
E.
namedAfterAirport
Indicates that one entity has been given a name derived from or in honor of a specific airport.
- 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_69f3496bda8c8190bfc8fade9d1b791c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:35 a.m.