Triple
T9514243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2nd U-boat Flotilla |
E229481
|
entity |
| Predicate | usedBaseType |
P32473
|
FINISHED |
| Object | U-boat bunker |
—
|
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 bunker | Statement: [2nd U-boat Flotilla, usedBaseType, U-boat bunker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedBaseType Context triple: [2nd U-boat Flotilla, usedBaseType, U-boat bunker]
-
A.
usesBase
Indicates that one entity relies on or operates using another entity as its foundational resource, framework, or reference point.
-
B.
baseType
chosen
Indicates that one entity serves as the underlying or parent type from which another entity is derived or specialized.
-
C.
usedInType
Indicates that something serves as a component, element, or example within a particular type or category.
-
D.
usesBaseline
Indicates that one entity relies on or applies another entity as a reference baseline for comparison, measurement, or evaluation.
-
E.
usedBaseArea
Indicates that one entity makes use of the base area (surface or footprint) of another entity for its function or calculation.
- 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_69ca84777560819084cddd999badc1aa |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd986bfcac8190aa97f8975cb17f6c |
completed | April 1, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cca567ca448190bf4bcce8ce7dd54f |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:58 p.m.