Triple
T22596821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Mauritius Command |
E574702
|
entity |
| Predicate | navalTheme |
P36018
|
FINISHED |
| Object | frigate 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: frigate warfare | Statement: [The Mauritius Command, navalTheme, frigate warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalTheme Context triple: [The Mauritius Command, navalTheme, frigate warfare]
-
A.
navalAnalogue
Indicates that one entity serves as the naval or maritime counterpart or equivalent of another entity in function, role, or classification.
-
B.
navalName
Indicates that an entity has a specific name used in a naval or maritime context.
-
C.
navalFeatures
chosen
Indicates that something possesses characteristics, components, or attributes specifically associated with naval or maritime contexts.
-
D.
navy
Indicates that an entity serves as or is associated with a nation's naval military force.
-
E.
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.
- 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_69e245bc11308190b69d794d5d1e0bb6 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f16269a56881909bb5af0258150f93 |
completed | April 29, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:50 p.m.