Triple
T8225870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EBBR |
E192170
|
entity |
| Predicate | hasTerminal |
P182
|
FINISHED |
| Object | Pier B |
E198639
|
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: Pier B | Statement: [EBBR, hasTerminal, Pier B]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pier B Context triple: [EBBR, hasTerminal, Pier B]
-
A.
Pier B
chosen
Pier B is one of the main passenger boarding concourses at Brussels Airport, primarily serving non-Schengen and long-haul international flights.
-
B.
Pier A
Pier A is a major passenger terminal concourse at Brussels Airport primarily serving Schengen and some non-Schengen flights.
-
C.
B Pier
B Pier is one of the passenger boarding concourses at Amsterdam Airport Schiphol, serving multiple gates for arriving and departing flights.
-
D.
Pier
Pier is a given name, commonly used in various European countries, that is derived from the name Pierre or Peter.
-
E.
Pier 3
Pier 3 is a historic waterfront pier along San Francisco’s Embarcadero, known for its maritime heritage and scenic views of the bay.
- 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_69ca82c9a8ac81908b011c38698456e4 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb77fc10f48190b7e241c89885a478 |
completed | March 31, 2026, 7:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd94d541f08190adf1fe7020b3c39b |
completed | April 1, 2026, 9:57 p.m. |
Created at: March 30, 2026, 5:45 p.m.