Triple
T26059962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amorbach |
E657230
|
entity |
| Predicate | hasRulingFamilyHistorically |
P25072
|
FINISHED |
| Object | House of Leiningen |
—
|
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 Leiningen | Statement: [Amorbach, hasRulingFamilyHistorically, House of Leiningen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRulingFamilyHistorically Context triple: [Amorbach, hasRulingFamilyHistorically, House of Leiningen]
-
A.
hasNotableDynastyMember
Indicates that a dynasty includes at least one member who is historically or culturally notable.
-
B.
hasRoyalAncestryFrom
Indicates that one entity possesses royal lineage or descent originating from another entity.
-
C.
hasBranchOfImperialFamily
Indicates that an entity includes or is associated with a specific branch or lineage of an imperial family.
-
D.
hasMajorDynasty
chosen
Indicates that an entity (such as a region, state, or historical period) is associated with or ruled by a particular major dynasty.
-
E.
historicalFamily
Indicates a familial relationship that existed between entities in the past, regardless of whether it still holds in the present.
- 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60c698ae48190871cd445422bad91 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 7:16 p.m.