Triple
T28244732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince-Bishop of Lübeck |
E712131
|
entity |
| Predicate | wasLinkedToDynasty |
P7426
|
FINISHED |
| Object | House of Oldenburg |
—
|
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: House of Oldenburg | Statement: [Prince-Bishop of Lübeck, wasLinkedToDynasty, House of Oldenburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasLinkedToDynasty Context triple: [Prince-Bishop of Lübeck, wasLinkedToDynasty, House of Oldenburg]
-
A.
associatedWithDynasty
chosen
Indicates that an entity has a historical, political, cultural, or familial connection to a specific dynasty.
-
B.
partOfDynasty
Indicates that an entity belongs to, or is a constituent member of, a particular dynasty.
-
C.
refersToPersonWithDynasty
Indicates that one entity makes reference to a person specifically identified or characterized by their association with a particular dynasty.
-
D.
associatedWithDynastyFoundation
Indicates a relationship in which an entity is connected to the founding or establishment of a particular dynasty.
-
E.
dynasticallyLinkedTo
Indicates a relationship where two entities are connected through a line of succession, inheritance, or familial rule within or across dynasties.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f643c84f1c8190879e643c18e74e75 |
completed | May 2, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 11 p.m.