Triple
T8234913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orion-class battleship |
E192380
|
entity |
| Predicate | commissionedPeriod |
P6782
|
FINISHED |
| Object | commissioned 1912 |
—
|
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: commissioned 1912 | Statement: [Orion-class battleship, commissionedPeriod, commissioned 1912]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commissionedPeriod Context triple: [Orion-class battleship, commissionedPeriod, commissioned 1912]
-
A.
commissionedDuring
Indicates that an entity was formally authorized, ordered, or initiated within a specified time period or event.
-
B.
commissionedAfter
Indicates that one entity was formally authorized, ordered, or initiated at a later time than another entity.
-
C.
commissionedAt
chosen
Indicates the time or date at which something (such as a work, project, or task) was formally commissioned or initiated.
-
D.
commissioningEndDate
Indicates the date on which the commissioning process or commissioning-related responsibilities are completed or terminated.
-
E.
commissionedWith
Indicates that one entity was created, produced, or initiated as part of the same commissioning event or request as another entity.
- 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_69ca82dc8f148190a2c75a98501a7b91 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb782931848190bcc54622f34e06a7 |
completed | March 31, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69cb36b1dea0819091418072501e79c1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:46 p.m.