Triple
T3248462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aden Adde International Airport |
E68118
|
entity |
| Predicate | hasCheckpoints |
P30109
|
FINISHED |
| Object | international departures security checkpoint |
—
|
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: international departures security checkpoint | Statement: [Aden Adde International Airport, hasCheckpoints, international departures security checkpoint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCheckpoints Context triple: [Aden Adde International Airport, hasCheckpoints, international departures security checkpoint]
-
A.
hasCheckpoint
chosen
Indicates that an entity includes, contains, or is associated with one or more intermediate control or verification points within its structure, process, or path.
-
B.
hasCheckpointType
Indicates that a checkpoint is associated with a specific type or category defining its role or characteristics.
-
C.
hadCheckpoint
Indicates that an entity passed through, reached, or was associated with a specific checkpoint at some point in time.
-
D.
hasCheckInCounters
Indicates that an entity is associated with one or more check-in counters used for processing arrivals or registrations.
-
E.
hasNumberOfTrails
Indicates the specific count of trails associated with or available in a given entity.
- 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_69ad858e4c708190aa31d486cfee8a6a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf3e9ed0819096ac238098ac403c |
completed | March 8, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69ada41837e48190933572165be0ca38 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.