Triple
T8059450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pozzo family |
E188081
|
entity |
| Predicate | typeOfDynasty |
P14587
|
FINISHED |
| Object | footballing dynasty |
—
|
LITERAL FINISHED |
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: footballing dynasty | Statement: [Pozzo family, typeOfDynasty, footballing dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfDynasty Context triple: [Pozzo family, typeOfDynasty, footballing dynasty]
-
A.
dynasticType
chosen
Indicates the specific kind or category of dynastic relationship or succession pattern that applies between ruling entities or lineages.
-
B.
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).
-
C.
dynasticOrigin
Indicates the historical dynasty or ruling family from which an entity originates or descends.
-
D.
dynasticStatus
Indicates the relationship between an entity and a ruling dynasty, such as membership in, association with, or status within that dynastic line.
-
E.
nativeDynasty
Indicates that a dynasty is indigenous to, or originally from, the place or polity it rules or is associated with.
- 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_69ca82b2f68881908c50560697e210da |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3fcaa8b8819099267564b6542547 |
completed | March 31, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69cb049cd51c8190bb3b0f503e42fa8d |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:25 p.m.