Triple
T30213119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaza International Airport |
E768123
|
entity |
| Predicate | runwayDestroyed |
P177159
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [Gaza International Airport, runwayDestroyed, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runwayDestroyed Context triple: [Gaza International Airport, runwayDestroyed, 2001]
-
A.
runwayConstructed
Indicates that a runway has been built or established at a particular location.
-
B.
runway
Indicates a relationship where a runway serves as the takeoff and landing surface used by aircraft at an airport or airfield.
-
C.
runwayOverrun
Indicates that an aircraft has continued past the designated end of the runway during landing or takeoff, exceeding the available runway length.
-
D.
runwayLanding
Indicates that an aircraft performs a landing operation on a specific runway.
-
E.
runwayUsedAs
Indicates that a particular runway is being utilized for a specific purpose, role, or operational function.
- 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6f85bfba48190aba95b40642a8ca7 |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f854486c81909396d944a55e03ab |
completed | May 3, 2026, 7:25 a.m. |
Created at: April 29, 2026, 7:33 p.m.