Triple
T26509264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holocaust in France |
E669632
|
entity |
| Predicate | collaborationRegime |
P99413
|
FINISHED |
| Object | État français |
—
|
NE NERFINISHED |
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: État français | Statement: [Holocaust in France, collaborationRegime, État français]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collaborationRegime Context triple: [Holocaust in France, collaborationRegime, État français]
-
A.
collaboratingRegime
chosen
Indicates that one regime is actively cooperating or working together with another regime toward shared goals or interests.
-
B.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
C.
collaborationScope
Indicates the extent, boundaries, and areas of responsibility covered by a particular collaboration between entities.
-
D.
collaborationRegion
Indicates the geographic or administrative area within which the collaboration between entities takes place or is defined.
-
E.
collaborationAspect
Indicates a specific characteristic, dimension, or feature of how entities collaborate or work together.
- 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 1:19 a.m.