Triple
T24038650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry I of Brunswick-Grubenhagen |
E595309
|
entity |
| Predicate | territoryCreated |
P145621
|
FINISHED |
| Object | Grubenhagen |
—
|
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: Grubenhagen | Statement: [Henry I of Brunswick-Grubenhagen, territoryCreated, Grubenhagen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: territoryCreated Context triple: [Henry I of Brunswick-Grubenhagen, territoryCreated, Grubenhagen]
-
A.
territorialAchievement
Indicates the acquisition, expansion, or consolidation of control over a geographic area by an entity.
-
B.
stateCreated
chosen
Indicates that a state or governmental entity was brought into existence or formally established by another agent or process.
-
C.
territoryAcquired
Indicates that one entity has gained control, ownership, or possession of a geographic area from another entity.
-
D.
territoryType
Indicates the specific kind or classification of a territory associated with an entity (e.g., country, region, zone, or jurisdiction type).
-
E.
laterTerritory
Indicates that one territory is a subsequent or successor territory to another in time.
- 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_69e288bf45f08190a1b6ed8cd0b9e86b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d8d6ce7c8190a41b2d9b459881bf |
completed | April 29, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:57 p.m.