Triple
T33142983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adelaide of Urslingen |
E848207
|
entity |
| Predicate | marriedIntoDynasty |
P4942
|
FINISHED |
| Object | Hohenstaufen 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: Hohenstaufen dynasty | Statement: [Adelaide of Urslingen, marriedIntoDynasty, Hohenstaufen dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriedIntoDynasty Context triple: [Adelaide of Urslingen, marriedIntoDynasty, Hohenstaufen dynasty]
-
A.
spouseDynasty
Indicates that there is a marital relationship linking an entity to the dynasty (family line or ruling house) of their spouse.
-
B.
marriedBy
Indicates that one entity is the officiant or authority who performs and formalizes the marriage of another entity.
-
C.
marriedInto
chosen
Indicates that one entity became connected to another’s family or group through marriage, rather than by birth or prior membership.
-
D.
marriedToHeiress
Indicates that a person is married to someone who is an heiress.
-
E.
formedByMarriageOf
Indicates that something (typically a family, union, or legal entity) comes into existence as a result of the marriage between two entities.
- 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_69f3495961d88190b16ea542c2c5f825 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 1, 2026, 1:28 a.m.