Triple
T3058116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Océan |
E60528
|
entity |
| Predicate | classLeadShip |
P44837
|
FINISHED |
| Object | Océan-class ship of the line |
—
|
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: Océan-class ship of the line | Statement: [Océan, classLeadShip, Océan-class ship of the line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classLeadShip Context triple: [Océan, classLeadShip, Océan-class ship of the line]
-
A.
statusOfLeadShip
Indicates the current condition or state assigned to the primary or leading ship in a given context or operation.
-
B.
coLeaderWith
Indicates that two or more entities share a joint leadership role or position with equal or comparable authority.
-
C.
captain
Indicates that one entity serves as the leader or person in command of another entity, typically a team, group, or vessel.
-
D.
leadingOrgan
Indicates that one entity serves as the primary or most responsible organizing body or authority for another entity or activity.
-
E.
headOfMission
Indicates that one entity serves as the chief or principal leader in charge of a specific mission or delegation.
- 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_69ad8578137c81908259dcb27c7d6d7c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9e162d148190969fb422a45d052c |
completed | March 8, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69ad962326e081909d5521c3d3ea3158 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f6af3881909f4547967384114c |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 3:02 p.m.