Triple
T24748460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baldassare Odescalchi |
E619069
|
entity |
| Predicate | familyInfluenceSphere |
P114304
|
FINISHED |
| Object | Papal States |
—
|
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: Papal States | Statement: [Baldassare Odescalchi, familyInfluenceSphere, Papal States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyInfluenceSphere Context triple: [Baldassare Odescalchi, familyInfluenceSphere, Papal States]
-
A.
familyInfluenceArea
chosen
Indicates the domain or scope within which a family exerts influence, impact, or control over something or someone.
-
B.
familyInvolvement
Indicates that there is participation, engagement, or influence of family members in the context of a particular activity, decision, or situation.
-
C.
parentInfluence
Indicates that one entity has a formative or guiding effect on another entity in the role of a parent.
-
D.
familyAspect
Indicates a relationship where one entity is characterized by a particular familial role, status, or aspect in relation to another entity.
-
E.
impactOnFamily
Indicates the effect or influence that something has on a family’s situation, dynamics, or well-being.
- 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_69e2fabb349881908a13a212a0221a63 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 4:24 a.m.