Triple
T28129594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3rd Battlecruiser Squadron |
E711024
|
entity |
| Predicate | navalHierarchyLevel |
P165427
|
FINISHED |
| Object | squadron |
—
|
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: squadron | Statement: [3rd Battlecruiser Squadron, navalHierarchyLevel, squadron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalHierarchyLevel Context triple: [3rd Battlecruiser Squadron, navalHierarchyLevel, squadron]
-
A.
navalRankContext
Indicates the relationship between an entity and its naval rank within a specific organizational, temporal, or situational context.
-
B.
navalRating
Indicates the assessed level of naval strength, capability, or performance attributed to an entity.
-
C.
navalRankFlagshipOf
Indicates that a naval rank is associated with, or designated as, the flagship command of, a particular vessel or fleet.
-
D.
navalTechnologyLevel
Indicates the relative advancement or sophistication of a party’s naval capabilities or maritime military technology.
-
E.
navalName
Indicates that an entity has a specific name used in a naval or maritime context.
- 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_69ef9b73bd288190a21ae3d6aa14f386 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f659355a208190be2609ffc7a9c427 |
completed | May 2, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f65875030881909007c502b7dcc998 |
completed | May 2, 2026, 8:03 p.m. |
Created at: April 27, 2026, 9:22 p.m.