Triple
T6950682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | canton of Orly |
E160912
|
entity |
| Predicate | administrativeCenter |
P1474
|
FINISHED |
| Object | Orly |
E65659
|
NE 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: Orly | Statement: [canton of Orly, administrativeCenter, Orly]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Orly Context triple: [canton of Orly, administrativeCenter, Orly]
-
A.
Orly
chosen
Orly is a commune in the southern suburbs of Paris, France, best known for giving its name to the nearby Paris Orly Airport.
-
B.
Orly
"Orly" is a poignant chanson by Belgian singer-songwriter Jacques Brel that reflects on love, separation, and farewell in the setting of Paris’s Orly Airport.
-
C.
Orly Sud
Orly Sud is the former name of Orly 4, a terminal facility at Paris Orly Airport in France.
-
D.
Ayelet
Ayelet is a feminine given name of Hebrew origin, commonly used in Israel.
-
E.
Orit
Orit is the traditional biblical canon of Ethiopian Jews, encompassing their sacred scriptures and guiding religious teachings.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c68850419081909fb426b8f5a304c7 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6daaeb66c8190a62b32a2c22f166a |
completed | March 27, 2026, 7:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c758797228819089362f137e9eb747 |
completed | March 28, 2026, 4:26 a.m. |
Created at: March 27, 2026, 2:29 p.m.