Triple
T10327487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SM U-9 |
E242795
|
entity |
| Predicate | navalPrefix |
P80388
|
FINISHED |
| Object | SM |
—
|
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: SM | Statement: [SM U-9, navalPrefix, SM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalPrefix Context triple: [SM U-9, navalPrefix, SM]
-
A.
navyDesignationPrefix
chosen
Indicates the specific naval designation or prefix assigned to an entity, typically reflecting its role, type, or status within a navy.
-
B.
navy
Indicates that an entity serves as or is associated with a nation's naval military force.
-
C.
navalCommand
Indicates a relationship where one entity holds authority to direct, control, or oversee naval forces or maritime military operations involving another entity.
-
D.
navalAnalogue
Indicates that one entity serves as the naval or maritime counterpart or equivalent of another entity in function, role, or classification.
-
E.
navalFleet
Indicates a relationship where multiple naval vessels are organized and operate together as a coordinated maritime military force.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7cf21e08190bf605daeea0d9dcf |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f64a648190a79980d647898eb0 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:51 a.m.