Triple
T25058636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boleslaus II the Pious |
E627593
|
entity |
| Predicate | consolidatedEntity |
P77053
|
FINISHED |
| Object | Přemyslid rule in Bohemia |
—
|
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: Přemyslid rule in Bohemia | Statement: [Boleslaus II the Pious, consolidatedEntity, Přemyslid rule in Bohemia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consolidatedEntity Context triple: [Boleslaus II the Pious, consolidatedEntity, Přemyslid rule in Bohemia]
-
A.
consolidatedBy
chosen
Indicates that one entity has been merged, unified, or combined into a more cohesive whole by another entity.
-
B.
consolidatedAs
Indicates that one entity has been combined, merged, or unified into another entity to form a single consolidated whole.
-
C.
consolidatedUnder
Indicates that one entity has been merged into and is now formally part of another, typically larger or parent, entity.
-
D.
consolidatedAfter
Indicates that one entity was formed or unified as a result of merging or combining multiple entities after a specified point in time.
-
E.
mergedEntityType
Indicates that one entity has been combined with another to form a single, unified entity type.
- 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_69e2ff2c45f48190afa28369f1df6786 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f45997265c8190938b57f5adf835ef |
completed | May 1, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:09 a.m.