Triple
T31318742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wolfsschlucht II |
E798665
|
entity |
| Predicate | locatedInCountryAtTimeOfUse |
P103056
|
FINISHED |
| Object | occupied France |
—
|
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: occupied France | Statement: [Wolfsschlucht II, locatedInCountryAtTimeOfUse, occupied France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInCountryAtTimeOfUse Context triple: [Wolfsschlucht II, locatedInCountryAtTimeOfUse, occupied France]
-
A.
locationCountryAtTheTime
chosen
Indicates that an entity was located in a specified country during a particular time or time period.
-
B.
locatedInCurrentCountry
Indicates that an entity is situated within the geographic boundaries of the country in which it is presently found.
-
C.
usedInConstituentCountry
Indicates that something is utilized or applied within a specific constituent country of a larger sovereign state.
-
D.
locatedInCountryDuringEvent
Indicates that an entity was situated within a specific country for the duration or at the time of a particular event.
-
E.
projectCountryAtTheTime
Indicates the country with which a project was associated at the specific time or period in question.
- 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a017bc21b048190b9c680013de203b6 |
completed | May 11, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_6a017aa09c4481909c3b55e0cd13501e |
completed | May 11, 2026, 6:43 a.m. |
Created at: April 29, 2026, 9:15 p.m.