Triple
T7387068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta King |
E170406
|
entity |
| Predicate | mooringStatus |
P8968
|
FINISHED |
| Object | permanently moored |
—
|
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: permanently moored | Statement: [Delta King, mooringStatus, permanently moored]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mooringStatus Context triple: [Delta King, mooringStatus, permanently moored]
-
A.
mooredInState
Indicates that an object such as a vessel or structure is secured or anchored within the territorial waters or jurisdiction of a specific state.
-
B.
mooredAt
chosen
Indicates that one object, typically a vessel or floating structure, is secured or anchored at a specific location or facility.
-
C.
sailingStatus
Indicates the current operational state or condition of a vessel in relation to its sailing activity (e.g., underway, docked, anchored, or out of service).
-
D.
berthingOrDockingTarget
Indicates that an entity serves as the location or structure where a vessel or vehicle is intended to berth or dock.
-
E.
marineProtectionStatus
Indicates the level or type of legal or regulatory protection applied to a marine area or resource.
- 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_69c68a5e2c9081909e713ce866e0060a |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f1f2bac481908ac74069182a4ce4 |
completed | March 27, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c6f0309cc88190b55d278969400294 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:08 p.m.