Triple
T10860712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 11th Armored Division |
E256393
|
entity |
| Predicate | deactivatedOn |
P95601
|
FINISHED |
| Object | 15 August 1945 |
—
|
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: 15 August 1945 | Statement: [11th Armored Division, deactivatedOn, 15 August 1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deactivatedOn Context triple: [11th Armored Division, deactivatedOn, 15 August 1945]
-
A.
deactivatedAt
chosen
Indicates the time or date at which an entity was disabled, turned off, or made inactive.
-
B.
deactivatedIn
Indicates that an entity has been turned off, disabled, or made inactive within a specified context, system, or time frame.
-
C.
deactivated
Indicates that an entity has been turned off, disabled, or rendered inactive so it no longer performs its usual function or role.
-
D.
inactivationReason
Indicates the reason or cause for which an entity, status, or process has been deactivated or made inactive.
-
E.
suspensionDate
Indicates the date on which an entity’s normal status, operation, or privileges are formally suspended.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7515186f08190a5cc388a7d936c4f |
completed | April 9, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d70d308dfc81908792f98cfb871392 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:20 p.m.