Triple
T24224689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odescalchi of Bassano |
E601560
|
entity |
| Predicate | nobleTitleHolderFamily |
P60633
|
FINISHED |
| Object | Odescalchi 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: Odescalchi family | Statement: [Odescalchi of Bassano, nobleTitleHolderFamily, Odescalchi family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleTitleHolderFamily Context triple: [Odescalchi of Bassano, nobleTitleHolderFamily, Odescalchi family]
-
A.
firstHolderNobleFamily
Indicates that a specified noble family was the first to hold a particular title, office, or possession.
-
B.
headOfNobleFamily
Indicates that one entity holds the position of leader or chief authority over a particular noble family.
-
C.
aristocraticTitleHeldBy
Indicates that a specific aristocratic or noble title is held or borne by a particular person.
-
D.
nobleTitleFrom
Indicates that a person derives or holds their noble title from a specified source, such as a place, lineage, or authority.
-
E.
titleHeldByFamily
chosen
Indicates that a particular title, rank, or honor is held collectively or traditionally by a specific family or family line.
- 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_69e29537ca548190b94a37ebe1977caf |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f287ddfecc81909f5396857974bc8c |
completed | April 29, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, midnight