Triple
T19460329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Kassel (1762) |
E486848
|
entity |
| Predicate | statusOfCityBefore |
P73538
|
FINISHED |
| Object | French-occupied city |
—
|
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: French-occupied city | Statement: [Siege of Kassel (1762), statusOfCityBefore, French-occupied city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfCityBefore Context triple: [Siege of Kassel (1762), statusOfCityBefore, French-occupied city]
-
A.
statusOfCityBeforeBattle
chosen
Indicates the condition or situation a city was in immediately prior to a specific battle.
-
B.
cityStatusUntil
Indicates the period up to a specified time during which a place holds or held a particular city status.
-
C.
previousMunicipalityStatus
Indicates that one municipality previously held a particular municipal status or classification before a change occurred.
-
D.
cityStatusGrantedInMemoryOf
Indicates that city status was conferred on a place specifically to honor or commemorate a particular person, event, or entity.
-
E.
cityStatusGrantedIn
Indicates the event or point in time at which an entity was officially granted city status in a particular place or jurisdiction.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633c7f4388190be8c207c94ba8889 |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.