Triple
T11066971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commune of Drancy |
E261649
|
entity |
| Predicate | worldWarIIEventPeriod |
P97611
|
FINISHED |
| Object | 1941–1944 |
—
|
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: 1941–1944 | Statement: [Commune of Drancy, worldWarIIEventPeriod, 1941–1944]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldWarIIEventPeriod Context triple: [Commune of Drancy, worldWarIIEventPeriod, 1941–1944]
-
A.
WWIIEvent
Indicates that the event is part of, or directly related to, the historical period and activities of World War II.
-
B.
statusDuringWorldWarII
Indicates the role, condition, or classification an entity had specifically during the period of World War II.
-
C.
sideInWorldWarII
Indicates that an entity was aligned with or participated on a particular side during World War II.
-
D.
worldWar
Indicates a large-scale armed conflict involving multiple nations across different regions of the world, typically encompassing numerous battles, alliances, and theaters of war.
-
E.
worldWarIService
Indicates that an entity served or participated in military service during World War I.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79920428c81908db824ab54e08e8d |
completed | April 9, 2026, 12:18 p.m. |
| PD | Predicate disambiguation | batch_69d74411d9e881908c0eeafa0f38e4b6 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750c99f9881908ee2b01b6ce4b3a1 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:26 p.m.