Triple
T8927812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elliott Bay Marina |
E212578
|
entity |
| Predicate | hasDockType |
P86238
|
FINISHED |
| Object | floating docks |
—
|
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: floating docks | Statement: [Elliott Bay Marina, hasDockType, floating docks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDockType Context triple: [Elliott Bay Marina, hasDockType, floating docks]
-
A.
hasPlatformType
Indicates that an entity is associated with or characterized by a specific type or category of platform.
-
B.
hasDropType
Indicates that an entity is associated with a specific type or category of drop (e.g., item, reward, or resource obtained).
-
C.
hasBoardType
Indicates that an entity is associated with or uses a specific type or category of board.
-
D.
hasPackageType
Indicates that an entity is associated with or classified under a particular type or category of package.
-
E.
hasDeckType
Indicates that an entity possesses or is associated with a specific type or category of deck.
- 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_69ca8395c438819087d7cb844ab5990c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6672af10819084a6e50f0302f732 |
completed | April 1, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed3286c8190a21de2ee11f2639f |
completed | March 31, 2026, 11:54 p.m. |
| PDg | Predicate description generation | batch_69cc608331f88190bcb500ff63527f8a |
completed | April 1, 2026, 12:02 a.m. |
Created at: March 30, 2026, 6:57 p.m.