Triple
T17172042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bourbon-Two Sicilies |
E416757
|
entity |
| Predicate | disputedHeadship |
P77973
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Bourbon-Two Sicilies, disputedHeadship, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disputedHeadship Context triple: [Bourbon-Two Sicilies, disputedHeadship, yes]
-
A.
disputed
Indicates that there is active disagreement or contestation over the validity, ownership, interpretation, or status of the relationship or claim between the entities.
-
B.
successorDisputesInvolved
chosen
Indicates involvement in disputes or conflicts arising from succession or succession-related claims.
-
C.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
-
D.
settledSuccessionDisputeBetween
Indicates that an entity resolved or brought to an end a conflict over inheritance or succession between two or more parties.
-
E.
disputedAspect
Indicates that a particular feature, detail, or component of something is subject to disagreement or contention between parties.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3fc0ac22481909e992bb3a6ba36ad |
completed | April 18, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.