Triple
T26486705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taiho-class aircraft carrier |
E664840
|
entity |
| Predicate | designedTimePeriod |
P14397
|
FINISHED |
| Object | early 1940s |
—
|
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: early 1940s | Statement: [Taiho-class aircraft carrier, designedTimePeriod, early 1940s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedTimePeriod Context triple: [Taiho-class aircraft carrier, designedTimePeriod, early 1940s]
-
A.
timePeriodFormulated
Indicates the time period during which something (such as a concept, theory, or plan) was formulated or developed.
-
B.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
C.
designPeriod
chosen
Indicates the time span during which something is planned, designed, or conceptually developed before implementation or production.
-
D.
hasDesignPeriod
Indicates that something was created, planned, or developed during a specified historical or stylistic design period.
-
E.
timePeriodProposed
Indicates that a specific time period has been suggested or put forward for consideration or adoption.
- 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_69ee883bc85481909885f92415cbce33 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 27, 2026, 12:31 a.m.