Triple
T661439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paris Orly Airport |
E11762
|
entity |
| Predicate | hasImmigration |
P7852
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Paris Orly Airport, hasImmigration, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImmigration Context triple: [Paris Orly Airport, hasImmigration, yes]
-
A.
immigrationBackground
Indicates that an entity has a personal or familial history of migration from another country or region.
-
B.
immigratedTo
Indicates that an entity moved from its country of origin to live permanently in another specified country or region.
-
C.
hasCustomsAndImmigration
chosen
Indicates that customs and immigration control services are present or provided at a given location or facility.
-
D.
numberOfImmigrantsProcessed
Indicates the total count of immigrants that have been processed in a given context or system.
-
E.
separateImmigrationSystemFrom
Indicates that one entity establishes or maintains a distinct immigration system that is independent from another entity’s immigration system.
- 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a0f55f7481909e052a25bd12d455 |
completed | March 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69a49d1406ec8190abf546549264c85d |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.