Triple
T20166468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Hermione |
E491835
|
entity |
| Predicate | enemyUnitType |
P99416
|
FINISHED |
| Object | U-boat |
—
|
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: U-boat | Statement: [HMS Hermione, enemyUnitType, U-boat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enemyUnitType Context triple: [HMS Hermione, enemyUnitType, U-boat]
-
A.
enemyType
Indicates that one entity is classified as an enemy of a specified type or category in relation to another entity.
-
B.
enemyForceType
chosen
Indicates that one entity is characterized as a hostile or opposing force of a specified type relative to another entity.
-
C.
typeOfFrontierUnit
Indicates that one unit is classified as a specific type or category of frontier unit in relation to another.
-
D.
enemyOrganization
Indicates that one organization is considered an adversary or opponent of another organization, typically in a hostile or competitive context.
-
E.
enemyTribe
Indicates that one tribe is in an adversarial or hostile relationship with another tribe.
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e66844e49081909b7e9ec2b65cc61d |
completed | April 20, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:35 p.m.