Triple
T18843499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RRS James Cook |
E460854
|
entity |
| Predicate | dynamicPositioningClass |
P67085
|
FINISHED |
| Object | DP2 |
—
|
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: DP2 | Statement: [RRS James Cook, dynamicPositioningClass, DP2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynamicPositioningClass Context triple: [RRS James Cook, dynamicPositioningClass, DP2]
-
A.
hasDynamicPositioning
chosen
Indicates that an entity is capable of automatically adjusting and maintaining its position relative to external references or conditions in real time.
-
B.
positionClass
Indicates the classification or category assigned to an entity based on its role, rank, or position within a defined structure or system.
-
C.
displacementClass
Indicates the category or type of physical displacement associated with an entity or event, typically grouping similar kinds or magnitudes of movement into a common class.
-
D.
positioning
Indicates the spatial or contextual arrangement of one entity relative to another or within a given environment.
-
E.
positioningSystems
Indicates a relationship where systems are used to determine, track, or control the spatial position or location of entities.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8ec8c5c8190b15e6394d0018573 |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.