Triple
T28936423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Elizabeth-class battleship |
E730328
|
entity |
| Predicate | commissionedInPeriod |
P5529
|
FINISHED |
| Object | 1914–1916 |
—
|
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: 1914–1916 | Statement: [Queen Elizabeth-class battleship, commissionedInPeriod, 1914–1916]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commissionedInPeriod Context triple: [Queen Elizabeth-class battleship, commissionedInPeriod, 1914–1916]
-
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.
compiledInPeriod
Indicates that the creation or compilation of something occurred within a specified time period.
-
D.
commissionedIn
chosen
Indicates that an entity was formally requested or authorized to be created, produced, or carried out in a specific time period or location.
-
E.
commissionedAt
Indicates the time or date at which something (such as a work, project, or task) was formally commissioned or initiated.
- 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 28, 2026, 8:32 a.m.