Triple
T35239873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luitpoldings |
E1017481
|
entity |
| Predicate | conflictedWithDynasty |
P37274
|
FINISHED |
| Object | Ottonian dynasty |
—
|
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: Ottonian dynasty | Statement: [Luitpoldings, conflictedWithDynasty, Ottonian dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictedWithDynasty Context triple: [Luitpoldings, conflictedWithDynasty, Ottonian dynasty]
-
A.
dynastyAffected
Indicates that a particular dynasty is influenced, impacted, or changed in some way by another entity, event, or condition.
-
B.
associatedWithDynasty
Indicates that an entity has a historical, political, cultural, or familial connection to a specific dynasty.
-
C.
dynasticRival
chosen
Indicates a relationship in which two entities belong to competing ruling lineages or houses that contest power or succession against each other.
-
D.
basedOnDynasty
Indicates that something is derived from, influenced by, or established on the foundation of a particular dynasty.
-
E.
possibleDynasty
Indicates that one entity could plausibly be the ruling dynasty associated with, or historically linked to, another entity.
- 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_69f76de235048190b990070c23c51b6b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:02 p.m.