Triple
T26457978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Endurance-class landing platform dock |
E665544
|
entity |
| Predicate | hasWellDeck |
P75730
|
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: [Endurance-class landing platform dock, hasWellDeck, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWellDeck Context triple: [Endurance-class landing platform dock, hasWellDeck, yes]
-
A.
hasVehicleDeck
Indicates that something (typically a vessel or structure) includes a dedicated deck or level designed for carrying or transporting vehicles.
-
B.
hasDryDock
Indicates that one entity possesses, contains, or is equipped with a dry dock facility used for servicing or repairing vessels out of the water.
-
C.
wellDeck
chosen
Indicates that one entity has a well deck feature or structure used for launching, recovering, or housing vessels or equipment.
-
D.
hasWharf
Indicates that one place or facility possesses or is equipped with a wharf for docking boats or ships.
-
E.
hasRailDeck
Indicates that something is equipped with or includes a deck specifically designed for carrying rail vehicles or tracks.
- 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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f61291b9588190931535163a538686 |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 12:10 a.m.