Triple
T32569871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isenburg-Offenbach |
E832483
|
entity |
| Predicate | fragmentationContext |
P174605
|
FINISHED |
| Object | existed within the fragmented Holy Roman Empire |
—
|
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: existed within the fragmented Holy Roman Empire | Statement: [Isenburg-Offenbach, fragmentationContext, existed within the fragmented Holy Roman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fragmentationContext Context triple: [Isenburg-Offenbach, fragmentationContext, existed within the fragmented Holy Roman Empire]
-
A.
aggregateContext
Indicates that one entity serves as a contextual grouping or container that collects, organizes, or summarizes information about another entity or set of entities.
-
B.
fragmentationLevel
Indicates the degree to which something is broken into smaller, separate parts or segments.
-
C.
separationContext
Indicates the situational or contextual factors under which two entities become separated or are considered distinct from one another.
-
D.
nowFragmentedInto
Indicates that an entity that was once whole has been broken or divided into multiple separate parts or fragments.
-
E.
unitContext
Indicates the contextual framework or setting (such as scope, conditions, or environment) within which a particular unit, instance, or occurrence is defined or interpreted.
- 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_69f34927bb308190ad94da1b11cad13c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c639c71481908bf86cbe33a33bbe |
completed | May 3, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 1:03 a.m.