Triple
T808468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amagi-class battlecruiser |
E17489
|
entity |
| Predicate | designedDuring |
P14116
|
FINISHED |
| Object | World War I era |
—
|
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: World War I era | Statement: [Amagi-class battlecruiser, designedDuring, World War I era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedDuring Context triple: [Amagi-class battlecruiser, designedDuring, World War I era]
-
A.
designedIn
Indicates that something was created, planned, or conceived during a particular time period or at a specific location.
-
B.
designPeriod
Indicates the time span during which something is planned, designed, or conceptually developed before implementation or production.
-
C.
hasDesignPeriod
chosen
Indicates that something was created, planned, or developed during a specified historical or stylistic design period.
-
D.
designDate
Indicates the date on which something was originally designed or its design was completed.
-
E.
introducedDuring
Indicates that one entity was first brought into existence, use, or awareness within the time period, event, or context specified by the other 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_69a4937ae8a08190b5084a03d532b30e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ac07fedc8190ab05595f25c1792f |
completed | March 1, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7221c081908068e66fe720f26d |
completed | March 1, 2026, 9:06 p.m. |
Created at: March 1, 2026, 7:38 p.m.