Triple
T15817403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Retvizan |
E383513
|
entity |
| Predicate | navalTechnologyEra |
P42687
|
FINISHED |
| Object | pre-dreadnought era |
—
|
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: pre-dreadnought era | Statement: [Retvizan, navalTechnologyEra, pre-dreadnought era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalTechnologyEra Context triple: [Retvizan, navalTechnologyEra, pre-dreadnought era]
-
A.
navalEra
chosen
Indicates the historical period or era in which a naval-related event, activity, or condition takes place.
-
B.
navalTechnologyLevel
Indicates the relative advancement or sophistication of a party’s naval capabilities or maritime military technology.
-
C.
navalTechnologySignificance
Indicates the importance or impact that a particular naval technology has within a given historical, strategic, or operational context.
-
D.
navalHistory
Indicates a relationship where an entity is associated with the study, record, or events of naval or maritime military history.
-
E.
propulsionEra
Indicates the historical period or generation of propulsion technology associated with an entity (e.g., vehicle, engine, or system).
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0c4a4332c8190bc525e06d6f3a6b4 |
completed | April 16, 2026, 11:14 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.