Triple
T3827721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Britannia |
E88730
|
entity |
| Predicate | navalTrainingType |
P52216
|
FINISHED |
| Object | pre-sea training |
—
|
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: pre-sea training | Statement: [HMS Britannia, navalTrainingType, pre-sea training]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalTrainingType Context triple: [HMS Britannia, navalTrainingType, pre-sea training]
-
A.
navalStandardType
Indicates the specific naval standard or classification system under which an entity (such as a vessel, equipment, or procedure) is defined or regulated.
-
B.
acquiredAsTrainingShip
Indicates that one entity obtained another specifically for use as a training ship.
-
C.
providesTrainingFor
Indicates that one entity delivers or conducts training activities intended to develop the skills or knowledge of another entity.
-
D.
typeOfCadetForce
Indicates the specific category or kind of cadet force to which an entity belongs.
-
E.
fleetType
Indicates the category or classification of a fleet to which an entity belongs or with which it is associated.
- 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_69aed9538cf881909d9ce8ca4ac7c18c |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeb8459f881908a2c91bb07e381ef |
completed | March 9, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69aee74c2e04819094b94b3c0bac1806 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aeeb828fb08190901d51edbe8bd304 |
completed | March 9, 2026, 3:47 p.m. |
Created at: March 9, 2026, 3:17 p.m.