Triple
T30213117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaza International Airport |
E768123
|
entity |
| Predicate | closedForTraffic |
P120271
|
FINISHED |
| Object | early 2000s |
—
|
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: early 2000s | Statement: [Gaza International Airport, closedForTraffic, early 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closedForTraffic Context triple: [Gaza International Airport, closedForTraffic, early 2000s]
-
A.
closedToAllTraffic
chosen
Indicates that the subject is not accessible or usable by any type of traffic.
-
B.
closedToThroughTraffic
Indicates that a route or area is not accessible for general passage and cannot be used as a through route for traffic.
-
C.
closedToMotorTraffic
Indicates that a route, road, or path is not accessible for use by motor vehicles.
-
D.
roadClosedIn
Indicates that a specific road is closed within a particular location or during a specified time or context.
-
E.
closedToScheduledTraffic
Indicates that an infrastructure element (such as a road, runway, or route) is not available for use by regular, planned, or scheduled traffic.
- 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 29, 2026, 7:33 p.m.