Triple
T16717080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Counts of Andechs-Meranien |
E406250
|
entity |
| Predicate | riseToPowerPeriod |
P46172
|
FINISHED |
| Object | late 11th century |
—
|
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: late 11th century | Statement: [Counts of Andechs-Meranien, riseToPowerPeriod, late 11th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riseToPowerPeriod Context triple: [Counts of Andechs-Meranien, riseToPowerPeriod, late 11th century]
-
A.
roseToPowerIn
chosen
Indicates the point in time or context in which an entity gained authority, control, or a dominant position.
-
B.
cameToPowerThrough
Indicates the manner or process by which an entity attained authority, leadership, or control, specifying how it rose to power.
-
C.
cameToPowerAfter
Indicates that one entity assumed authority or control following the rule or tenure of another entity.
-
D.
roseToPowerThrough
Indicates the means, process, or circumstances by which an entity gained authority, control, or a dominant position.
-
E.
roseToProminenceIn
Indicates the time or context in which an entity became widely recognized, influential, or notable.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e38656b66081909f2c2a8971c45aee |
completed | April 18, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.