Triple
T9977619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pier A |
E196371
|
entity |
| Predicate | hasName |
P744
|
FINISHED |
| Object | Pier A |
E196371
|
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 A | Statement: [Pier A, hasName, Pier A]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pier A Context triple: [Pier A, hasName, Pier A]
-
A.
Pier A
chosen
Pier A is a major passenger terminal concourse at Brussels Airport primarily serving Schengen and some non-Schengen flights.
-
B.
Pier 5
Pier 5 is a recreational pier in Brooklyn Bridge Park known for its sports fields, waterfront views, and public gathering spaces along the Brooklyn waterfront.
-
C.
Pier 2
Pier 2 is a waterfront recreational pier in Brooklyn Bridge Park known for its sports courts, roller rink, and panoramic views of New York Harbor.
-
D.
Pier 4
Pier 4 is a waterfront pier and recreational area within Brooklyn Bridge Park in Brooklyn, New York City.
-
E.
Pier 15
Pier 15 is a modern two-level waterfront pier in Lower Manhattan offering public green space, East River views, and access to boats and recreational activities.
- 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_69ca82eea2b88190a0e511d21a31f386 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb84ef8ac8190abbe78b7611c5309 |
completed | April 2, 2026, 12:29 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d23dec07b48190a2c15a748324291b |
completed | April 5, 2026, 10:48 a.m. |
Created at: March 30, 2026, 8:48 p.m.