Triple
T17318534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fuji-class battleship |
E420494
|
entity |
| Predicate | launchedInPeriod |
P47823
|
FINISHED |
| Object | 1896 |
—
|
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: 1896 | Statement: [Fuji-class battleship, launchedInPeriod, 1896]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchedInPeriod Context triple: [Fuji-class battleship, launchedInPeriod, 1896]
-
A.
appliedDuringPeriod
Indicates that an action, condition, or status was in effect throughout a specified time period.
-
B.
launchPeriod
chosen
Indicates the time span during which a launch or deployment activity occurs or is valid.
-
C.
isSetInTimePeriod
Indicates that an event, story, or situation takes place within a specified time period.
-
D.
launchedAt
Indicates the specific time or event at which something (such as a product, project, or mission) was initiated or set into operation.
-
E.
recordedInPeriodStart
Indicates that an event or record began or was first documented at the start of a specified time period.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4399f84a881908dd99ecd7cc02708 |
completed | April 19, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:43 a.m.