Triple
T32437212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Farragut (DD-300) |
E828906
|
entity |
| Predicate | launchedInEra |
P117687
|
FINISHED |
| Object | post–World War I |
—
|
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: post–World War I | Statement: [USS Farragut (DD-300), launchedInEra, post–World War I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchedInEra Context triple: [USS Farragut (DD-300), launchedInEra, post–World War I]
-
A.
usedDuringEraOf
Indicates that something was in use or actively employed during the time period or historical era associated with another entity.
-
B.
livedInEra
chosen
Indicates that an entity existed or was active during a particular historical era or time period.
-
C.
appliesToEra
Indicates that something is relevant, valid, or in effect during a particular historical or temporal era.
-
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.
historicalEraUsheredIn
Indicates the historical era or period that was initiated or brought about as a result of a particular event, action, or entity.
- 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_69f3491bf298819097b610f772d54a6d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 12:55 a.m.