Triple
T31026588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pier 62 (Seattle) |
E790590
|
entity |
| Predicate | isNumberedPier |
P170926
|
FINISHED |
| Object | 62 |
—
|
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: 62 | Statement: [Pier 62 (Seattle), isNumberedPier, 62]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNumberedPier Context triple: [Pier 62 (Seattle), isNumberedPier, 62]
-
A.
isNumberedPierOf
Indicates that one entity is a specific numbered pier belonging to or associated with another entity (such as a port, harbor, or waterfront facility).
-
B.
hasPierNumberRange
Indicates that an entity is associated with a continuous range of pier numbers, from a starting pier number to an ending pier number.
-
C.
hasPiersOn
Indicates that one structure or location is supported or extended by piers that are physically situated on another structure or surface.
-
D.
numberOfPiers
Indicates the quantity of piers associated with or present in a given structure, location, or context.
-
E.
hasPierName
Indicates that an entity (such as a berth, dock, or mooring location) is associated with a specific pier name.
- F. None of above. chosen
Provenance (4 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 29, 2026, 8:58 p.m.