Triple
T23133360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mainz-Kostheim |
E577239
|
entity |
| Predicate | locatedInOccupationZoneAfterWWII |
P151045
|
FINISHED |
| Object | American occupation zone |
—
|
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: American occupation zone | Statement: [Mainz-Kostheim, locatedInOccupationZoneAfterWWII, American occupation zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInOccupationZoneAfterWWII Context triple: [Mainz-Kostheim, locatedInOccupationZoneAfterWWII, American occupation zone]
-
A.
exileLocationDuringWorldWarII
Indicates the place where an entity was in exile specifically during World War II.
-
B.
postWarOccupation
Indicates that one entity occupied, administered, or controlled another entity or territory in the period following a war.
-
C.
postWarLocation
Indicates the place where an entity is located or based after a war or major conflict has ended.
-
D.
wasOccupiedDuringWar
Indicates that a place or territory was under military or foreign control for some period during a specified war.
-
E.
preWarOccupation
Indicates the occupation or role a person held before a specific war or armed conflict.
- 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_69e245f7b0e481909c473ff4e6a54e2c |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e89cce881908727a94dbc00e031 |
completed | April 29, 2026, 4:52 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 4 p.m.