Triple
T13634505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German military |
E325812
|
entity |
| Predicate | foundedAsBundeswehr |
P74567
|
FINISHED |
| Object | 1955 |
—
|
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: 1955 | Statement: [German military, foundedAsBundeswehr, 1955]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsBundeswehr Context triple: [German military, foundedAsBundeswehr, 1955]
-
A.
militaryOrigin
Indicates that an entity originates from, was created by, or is derived from a military organization, context, or background.
-
B.
militaryUnitFounded
chosen
Indicates that a specific military unit was established or created at a particular time or by a particular founding action.
-
C.
militaryBranchComponentOf
Indicates that one military branch or unit is an organizational component or subordinate part of a larger military branch or force.
-
D.
militaryOrganization
Indicates that an entity functions as, or is associated with, a structured armed forces or defense-related organization.
-
E.
militaryBranchAssociatedWith
Indicates a relationship where an entity is connected to, or operates as part of, a specific branch of a military organization.
- 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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc60635d08190899806fe8936f02a |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe85e1c4819095194f4b7f9f6118 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:51 p.m.