Triple
T12695405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryūjō-class aircraft carrier |
E303318
|
entity |
| Predicate | timePeriodOfService |
P75989
|
FINISHED |
| Object | 1930s |
—
|
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: 1930s | Statement: [Ryūjō-class aircraft carrier, timePeriodOfService, 1930s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfService Context triple: [Ryūjō-class aircraft carrier, timePeriodOfService, 1930s]
-
A.
hasTimePeriodOfService
chosen
Indicates that an entity is associated with a specific span of time during which it provided service or was actively serving.
-
B.
typicalTimeInServiceToAttain
Indicates the usual duration of service required for an entity to reach or attain a specified status, level, or condition.
-
C.
militaryServicePeriod
Indicates the span of time during which an entity serves or has served in a military capacity.
-
D.
serviceEntryPeriod
Indicates the span of time during which a service is active, valid, or in effect for the related entities.
-
E.
eligibilityPeriod
Indicates the span of time during which an entity qualifies for or is allowed to receive a particular benefit, service, or status.
- 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_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d962a32c6481908ddaddae4ea267bf |
completed | April 10, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69d960be63f081908a5ef5ef17a311bf |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:22 p.m.