Triple
T11501156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lydda Airport |
E272665
|
entity |
| Predicate | currentRoleOfSite |
P16008
|
FINISHED |
| Object | Israel’s primary international gateway |
—
|
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: Israel’s primary international gateway | Statement: [Lydda Airport, currentRoleOfSite, Israel’s primary international gateway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentRoleOfSite Context triple: [Lydda Airport, currentRoleOfSite, Israel’s primary international gateway]
-
A.
siteRole
Indicates the specific function, responsibility, or position an entity holds within a particular site or location.
-
B.
currentSiteUse
chosen
Indicates how a site is presently being used or the function it currently serves.
-
C.
ClientRole
Indicates that an entity participates in a relationship or interaction specifically in the capacity of a client.
-
D.
canonicalRole
Indicates that an entity holds a standard, primary, or officially recognized role within a particular context or system.
-
E.
typeOfSite
Indicates the specific category or kind of site that an entity is classified as.
- 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d85de3e9c881909d6c55334f7a832d |
completed | April 10, 2026, 2:18 a.m. |
| PD | Predicate disambiguation | batch_69d808736c5c8190899b5b3b2e797f65 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.