Triple
T32983692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isenburg-Birstein |
E843876
|
entity |
| Predicate | nobleTerritoryOf |
P86992
|
FINISHED |
| Object | House of Isenburg |
—
|
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: House of Isenburg | Statement: [Isenburg-Birstein, nobleTerritoryOf, House of Isenburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleTerritoryOf Context triple: [Isenburg-Birstein, nobleTerritoryOf, House of Isenburg]
-
A.
nobleFamilyTerritory
chosen
Indicates that a noble family holds dominion, control, or traditional rights over a specific geographic territory.
-
B.
wasCoreTerritoryOf
Indicates that a region historically formed the central or most important territorial area belonging to a particular political or cultural entity.
-
C.
mainTerritoryOfInfluence
Indicates the primary geographic area where an entity exerts the most significant control, impact, or influence.
-
D.
indigenousTerritoryOf
Indicates that a geographic area is traditionally inhabited, used, or claimed by a particular Indigenous people or community as their ancestral territory.
-
E.
territorialPower
Indicates that an entity holds governing authority or control over a specific geographic territory.
- 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_69f3494c6f9c8190a255409fce8b1d3b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:22 a.m.