Triple
T661438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paris Orly Airport |
E11762
|
entity |
| Predicate | hasCustoms |
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, hasCustoms, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCustoms Context triple: [Paris Orly Airport, hasCustoms, yes]
-
A.
hasCustomsAndImmigration
chosen
Indicates that customs and immigration control services are present or provided at a given location or facility.
-
B.
customs
Indicates that an entity is responsible for regulating, inspecting, or processing goods and people as they cross a border for legal and tax purposes.
-
C.
customsInstrument
Indicates that one entity serves as a tool, method, or means used by customs authorities to perform or facilitate a customs-related action involving another entity.
-
D.
customsRegime
Indicates the specific customs treatment or regulatory framework under which goods are imported, exported, or stored.
-
E.
hasCustomsUnion
Indicates that two or more entities participate in a customs union, sharing a common external tariff and removing customs duties between them.
- 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.