Triple
T23237212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Acasta |
E581334
|
entity |
| Predicate | navalRatingSystem |
P27155
|
FINISHED |
| Object | British Royal Navy rating system |
—
|
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: British Royal Navy rating system | Statement: [HMS Acasta, navalRatingSystem, British Royal Navy rating system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalRatingSystem Context triple: [HMS Acasta, navalRatingSystem, British Royal Navy rating system]
-
A.
navalRating
Indicates the assessed level of naval strength, capability, or performance attributed to an entity.
-
B.
navalRankContext
Indicates the relationship between an entity and its naval rank within a specific organizational, temporal, or situational context.
-
C.
navalStandardType
chosen
Indicates the specific naval standard or classification system under which an entity (such as a vessel, equipment, or procedure) is defined or regulated.
-
D.
navalDiscipline
Indicates the enforcement or maintenance of rules, order, and conduct within a naval or maritime context.
-
E.
navalClassGeneration
Indicates that one naval class belongs to a particular generational sequence or iteration relative to another naval class.
- 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_69e2460556f88190be1744a84a84173f |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f192ea590c81908cd677d89f67d49f |
completed | April 29, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69effcdadec0819092ec1749ee453b4e |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:09 p.m.