Triple
T36258426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EgyptAir Cargo |
E892010
|
entity |
| Predicate | hasCargoTerminalAccess |
P124919
|
FINISHED |
| Object | Cairo Cargo Terminal |
—
|
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: Cairo Cargo Terminal | Statement: [EgyptAir Cargo, hasCargoTerminalAccess, Cairo Cargo Terminal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCargoTerminalAccess Context triple: [EgyptAir Cargo, hasCargoTerminalAccess, Cairo Cargo Terminal]
-
A.
hasCargoTerminal
Indicates that a location or facility includes or is equipped with a cargo terminal for handling freight.
-
B.
hasCargoAccess
chosen
Indicates that an entity has the ability or permission to access a designated cargo area or its contents.
-
C.
hasBorderFacilityAccess
Indicates that an entity is permitted to enter, use, or operate within a designated border facility or checkpoint.
-
D.
hasContainerTerminal
Indicates that one entity possesses, includes, or is associated with a container terminal as part of its facilities or infrastructure.
-
E.
hasPassengerTerminal
Indicates that one entity possesses or is equipped with a passenger terminal used for boarding, alighting, or handling passengers.
- 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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffbb1c5bf88190a0bf791213045885 |
completed | May 9, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69ffba0ab0f881908f84ef81f7a1bfe8 |
completed | May 9, 2026, 10:49 p.m. |
Created at: May 3, 2026, 4:09 p.m.