Triple
T34438977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estonian military ranks |
E884045
|
entity |
| Predicate | hasNavalRank |
P198889
|
FINISHED |
| Object | admiral |
—
|
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: admiral | Statement: [Estonian military ranks, hasNavalRank, admiral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNavalRank Context triple: [Estonian military ranks, hasNavalRank, admiral]
-
A.
hasNotableNavalRank
Indicates that an entity holds or has held a distinguished or significant rank within a naval organization.
-
B.
navalRankContext
Indicates the relationship between an entity and its naval rank within a specific organizational, temporal, or situational context.
-
C.
hasNavalRole
Indicates that an entity holds or is assigned a role, function, or duty within a naval or maritime context.
-
D.
isHighestActiveNavyRank
Indicates that the subject holds the highest currently active rank within a navy, above all other active naval ranks.
-
E.
navalHierarchyLevel
Indicates the relative rank or position of an entity within a naval command or organizational hierarchy.
- F. None of above. chosen
Provenance (4 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_69f349c548d88190978e2a82502c03d0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff109695008190a22b47ef8be2e3f9 |
completed | May 9, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69ff0f243ea88190970d2c520b55c816 |
completed | May 9, 2026, 10:40 a.m. |
| PDg | Predicate description generation | batch_69ff10956d3881909144f880f92e90c4 |
completed | May 9, 2026, 10:46 a.m. |
Created at: May 1, 2026, 2 a.m.