Triple
T8739468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | heavy cruiser Maya |
E207464
|
entity |
| Predicate | refitPeriod |
P3155
|
FINISHED |
| Object | 1943-1944 |
—
|
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: 1943-1944 | Statement: [heavy cruiser Maya, refitPeriod, 1943-1944]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refitPeriod Context triple: [heavy cruiser Maya, refitPeriod, 1943-1944]
-
A.
refit
chosen
Indicates that an existing object or structure is being modified, repaired, or equipped with new parts or features to restore or improve its function.
-
B.
restatementPeriod
Indicates the time span over which something is restated, revised, or reissued, typically referring to a defined interval covered by a correction or updated version.
-
C.
rebuildPeriod
Indicates the time span during which something is reconstructed or restored after damage, failure, or decommissioning.
-
D.
timePeriodOfRefinement
Indicates the specific time span during which a refinement or improvement of something takes place.
-
E.
reorganizationPeriod
Indicates the time span during which a structural or organizational change is planned, underway, or in effect.
- 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_69ca835a03a081909d4d4cd01a18c9fb |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d486e34819094a6c6ec26c047cf |
completed | March 31, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69cc457322b481908712a9630a17b954 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:38 p.m.