Triple
T36609066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cité de la Muette housing complex |
E903418
|
entity |
| Predicate | operatedAsCampBy |
P36647
|
FINISHED |
| Object | Nazi Germany |
E1491
|
NE 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: Nazi Germany | Statement: [Cité de la Muette housing complex, operatedAsCampBy, Nazi Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedAsCampBy Context triple: [Cité de la Muette housing complex, operatedAsCampBy, Nazi Germany]
-
A.
periodOfUseAsCamp
Indicates the span of time during which a place or facility was used as a camp.
-
B.
administeredCamp
Indicates that an entity was responsible for managing, organizing, or overseeing the operation of a particular camp.
-
C.
campingManagedBy
Indicates that the organization or entity specified is responsible for managing, operating, or overseeing the camping activity, site, or facility.
-
D.
refugeeCampOperatedFrom
Indicates that a refugee camp is administered, managed, or run by a specified organization, authority, or entity.
-
E.
operatedConcentrationCamp
chosen
Indicates that an entity was responsible for running, managing, or administering the operations of a concentration camp.
- F. None of above.
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_69f76e6960e4819092047756ceb9a17e |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a01b841f5508190832bba00cf795bad |
completed | May 11, 2026, 11:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39f92bb0808190b163b57d52515a4c |
completed | June 23, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_6a01b59541fc8190a9b13a55327c4aa1 |
completed | May 11, 2026, 10:55 a.m. |
Created at: May 3, 2026, 4:11 p.m.