Triple
T5709817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florida-class battleship |
E125877
|
entity |
| Predicate | timePeriodOfDesign |
P14397
|
FINISHED |
| Object | 1900s |
—
|
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: 1900s | Statement: [Florida-class battleship, timePeriodOfDesign, 1900s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfDesign Context triple: [Florida-class battleship, timePeriodOfDesign, 1900s]
-
A.
designPeriod
chosen
Indicates the time span during which something is planned, designed, or conceptually developed before implementation or production.
-
B.
designedReturnPeriod
Indicates the length of time for which something is intentionally engineered or planned to remain effective, reliable, or valid.
-
C.
hasDesignPeriod
Indicates that something was created, planned, or developed during a specified historical or stylistic design period.
-
D.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
E.
designLifetime
Indicates the intended duration or operational period for which something is designed to function as specified.
- 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_69c0082d6fe48190b777fb383769e5c8 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0248c3dac8190824fca9ddde89665 |
completed | March 22, 2026, 5:19 p.m. |
| PD | Predicate disambiguation | batch_69c021c2d8bc8190b947c7d1f423d2f3 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:46 p.m.