Triple
T26857793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Navy minesweepers |
E676241
|
entity |
| Predicate | crewSpecialization |
P21064
|
FINISHED |
| Object | divers |
—
|
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: divers | Statement: [Royal Navy minesweepers, crewSpecialization, divers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewSpecialization Context triple: [Royal Navy minesweepers, crewSpecialization, divers]
-
A.
crewType
chosen
Indicates the specific role or category of crew associated with an entity, such as the type of personnel assigned to operate or support it.
-
B.
unitSpecialization
Indicates that one unit is a specialized or more specific version of another unit within a hierarchical or categorical relationship.
-
C.
crewComplementType
Indicates the classification or category of a crew complement associated with an entity (such as its role, composition, or staffing type).
-
D.
aircraftRoleSpecialization
Indicates that one aircraft role is a more specific, specialized form of another, more general aircraft role.
-
E.
creatorSpecialization
Indicates the specific field, discipline, or area of expertise in which a creator primarily works or is specialized.
- 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_69eee9b9d7708190a15d7485709ae981 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 5:22 a.m.