Triple
T26027202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | מחוז הדרום |
E647324
|
entity |
| Predicate | כולל נמל תעופה בינלאומי |
P1813
|
FINISHED |
| Object | נמל התעופה רמון |
—
|
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: נמל התעופה רמון | Statement: [מחוז הדרום, כולל נמל תעופה בינלאומי, נמל התעופה רמון]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: כולל נמל תעופה בינלאומי Context triple: [מחוז הדרום, כולל נמל תעופה בינלאומי, נמל התעופה רמון]
-
A.
hasInternationalAirport
chosen
Indicates that a place possesses an airport that handles international flights and services cross-border air traffic.
-
B.
isOnlyInternationalAirportOf
Indicates that an airport is the single, unique international airport serving a particular city, region, or country.
-
C.
hubAirport
Indicates that an airport serves as a primary hub or central operating base for a particular airline or carrier.
-
D.
isCivilAirport
Indicates that an airport is designated and used primarily for civilian (non-military) aviation operations.
-
E.
airportOfficialName
Indicates the officially designated full name of an airport as recognized by authorities or governing bodies.
- 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 22, 2026, 9:05 a.m.