Triple
T18916783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marina Real británica |
E462743
|
entity |
| Predicate | periodoDeHegemoníaNaval |
P42687
|
FINISHED |
| Object | aprox. 1815–1914 |
—
|
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: aprox. 1815–1914 | Statement: [Marina Real británica, periodoDeHegemoníaNaval, aprox. 1815–1914]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodoDeHegemoníaNaval Context triple: [Marina Real británica, periodoDeHegemoníaNaval, aprox. 1815–1914]
-
A.
navalEra
chosen
Indicates the historical period or era in which a naval-related event, activity, or condition takes place.
-
B.
navalHistory
Indicates a relationship where an entity is associated with the study, record, or events of naval or maritime military history.
-
C.
maritimeExpansion
Indicates the process by which an entity extends its influence, activities, or control over new maritime areas, routes, or territories.
-
D.
navalOpposition
Indicates a relationship where one party actively resists, confronts, or acts against another using naval or maritime military forces.
-
E.
countryNavalForce
Indicates that a country possesses, controls, or is associated with a particular naval military force.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c627724881909cf63c67d64321e8 |
completed | April 20, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.