Triple
T33047647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Island of Leucada |
E845637
|
entity |
| Predicate | ruledByFamily |
P9023
|
FINISHED |
| Object | Orsini family |
—
|
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: Orsini family | Statement: [Island of Leucada, ruledByFamily, Orsini family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruledByFamily Context triple: [Island of Leucada, ruledByFamily, Orsini family]
-
A.
monarchInFamily
Indicates that a member of a family holds (or held) the position of monarch within that family lineage.
-
B.
rulingHouse
chosen
Indicates that one entity serves as the dynastic or noble family that holds ruling authority over another entity, such as a state, territory, or polity.
-
C.
formerRulerHouse
Indicates that a person once ruled on behalf of, or as a member of, a particular ruling house or dynasty but no longer holds that ruling position.
-
D.
regentDynasty
Indicates that one entity served as the ruling dynasty or regent house governing on behalf of another entity (such as a realm, monarch, or territory).
-
E.
partOfDynasty
Indicates that an entity belongs to, or is a constituent member of, a particular dynasty.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:24 a.m.