Triple
T7465281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vessel |
E176356
|
entity |
| Predicate | hasViewingPlatforms |
P13017
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Vessel, hasViewingPlatforms, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViewingPlatforms Context triple: [Vessel, hasViewingPlatforms, yes]
-
A.
hasViewingPlatform
chosen
Indicates that an entity includes or is equipped with a designated platform or area intended for viewing or observing something.
-
B.
hasOutdoorPlatforms
Indicates that an entity includes one or more platforms or boarding areas that are located outdoors rather than inside a building or covered structure.
-
C.
hasScenicViewOf
Indicates that one entity offers a visually appealing or picturesque view of another entity.
-
D.
hasIslandPlatforms
Indicates that the subject has one or more island-style platforms, typically positioned between tracks and accessible from both sides.
-
E.
hasSidePlatforms
Indicates that something is equipped with platforms located on its sides, typically for access, support, or operation.
- F. None of above.
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_69c69f21632481908bf83f6c6da897e3 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3f28f34819080713a8abcc22034 |
completed | March 27, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c6f03bad9c8190bdd5abb86d37df47 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:40 p.m.