Triple
T675679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orly 4 |
E13071
|
entity |
| Predicate | connectedTo |
P37
|
FINISHED |
| Object | Orly 1-2-3 |
E10908
|
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 1-2-3 | Statement: [Orly 4, connectedTo, Orly 1-2-3]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Orly 1-2-3 Context triple: [Orly 4, connectedTo, Orly 1-2-3]
-
A.
Orly 3
Orly 3 is one of the main passenger terminals at Paris Orly Airport, serving as a hub for check-in, boarding, and arrivals operations.
-
B.
Orly 2
Orly 2 is one of the main passenger terminals at Paris Orly Airport, serving as a hub for various domestic and international flights.
-
C.
Orly 4
Orly 4 is one of the main passenger terminals at Paris Orly Airport, serving as a hub for various domestic and international flights.
-
D.
Orly 1
chosen
Orly 1 is one of the passenger terminals at Paris Orly Airport, serving as a key facility for check-in, boarding, and arrivals operations.
-
E.
Orly
Orly is a commune in the southern suburbs of Paris, France, best known for giving its name to the nearby Paris Orly Airport.
- 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_69a4933d3bf88190972041cd8cf143b9 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a0266e7c8190a94c4b4b761c59f4 |
completed | March 1, 2026, 8:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a654d625608190814bec3b412c86d7 |
completed | March 3, 2026, 3:26 a.m. |
Created at: March 1, 2026, 7:36 p.m.