Triple
T20817591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type 212CD-class submarine |
E512481
|
entity |
| Predicate | numberOrderedByGermany |
P141943
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Type 212CD-class submarine, numberOrderedByGermany, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOrderedByGermany Context triple: [Type 212CD-class submarine, numberOrderedByGermany, 2]
-
A.
objectiveGermany
Indicates that an entity has Germany as its objective, target, or goal in a given context.
-
B.
lengthInGermany
Indicates the extent or duration of something measured specifically within the geographic or jurisdictional boundaries of Germany.
-
C.
rankAmongGermanStates
Indicates the relative position or standing of a German state when ordered or compared to other German states by a specific criterion (such as size, population, or performance).
-
D.
locatedInPartOfGermany
Indicates that one entity is geographically situated within a specific region or part of Germany.
-
E.
rankWithinGermanStates
Indicates the relative position or standing of an entity compared to others within the set of German federal states.
- 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_69e0b4cd25088190b48ca9700cd24efc |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2f429388190809dd532278fe310 |
completed | April 21, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:41 p.m.