Triple
T719130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pascual Cervera y Topete |
E14376
|
entity |
| Predicate | navalWarfareDomain |
P17742
|
FINISHED |
| Object | surface warfare |
—
|
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: surface warfare | Statement: [Pascual Cervera y Topete, navalWarfareDomain, surface warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalWarfareDomain Context triple: [Pascual Cervera y Topete, navalWarfareDomain, surface warfare]
-
A.
navalDoctrineImpact
Indicates how a particular naval doctrine influences or alters the effectiveness, behavior, or outcomes of naval forces or operations.
-
B.
militaryDomain
chosen
Indicates that the relationship or action occurs within, pertains to, or is specifically associated with the military sphere or context.
-
C.
navalAccess
Indicates that one entity has the right or ability to use another entity’s naval facilities, waters, or maritime routes for military or strategic purposes.
-
D.
navalFleet
Indicates a relationship where multiple naval vessels are organized and operate together as a coordinated maritime military force.
-
E.
includedNavalBattle
Indicates that one entity participated in or contained a specific naval battle as part of its events or composition.
- 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_69a4934a36e081909e7abef98b898a4e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a58d4c3c8190ad4527d14bca5e6e |
completed | March 1, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f513608190b716b939d574c292 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.