Triple
T4988728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ninth Army |
E112073
|
entity |
| Predicate | finalRole |
P51151
|
FINISHED |
| Object | defense of Berlin |
—
|
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: defense of Berlin | Statement: [Ninth Army, finalRole, defense of Berlin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalRole Context triple: [Ninth Army, finalRole, defense of Berlin]
-
A.
finalAct
Indicates that an action or event is the last or concluding act in a sequence or process.
-
B.
finalRuler
Indicates that an entity is the last or ultimate ruler of another entity, with no subsequent rulers following.
-
C.
deFactoRole
Indicates that an entity effectively functions in a role or capacity in practice, even if that role is not formally or officially assigned.
-
D.
finalPhaseOf
Indicates that one process, stage, or event constitutes the concluding or last phase of another broader process or sequence.
-
E.
effectiveRole
chosen
Indicates the functional role or capacity an entity actually performs or holds in a given context, regardless of its formal or nominal designation.
- 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_69bd441be7bc8190b530362d427b97d2 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74249a8c8190952680aee06a9286 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd71492dec8190af4c27a3043b35cc |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:34 p.m.