Triple
T15562545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Carignano |
E371033
|
entity |
| Predicate | dynasticRank |
P19583
|
FINISHED |
| Object | junior branch |
—
|
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: junior branch | Statement: [Prince of Carignano, dynasticRank, junior branch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynasticRank Context triple: [Prince of Carignano, dynasticRank, junior branch]
-
A.
dynasticOrder
Indicates the hierarchical sequence of rulers or family lines within a dynasty, specifying who precedes or follows whom in dynastic succession.
-
B.
dynasticNumber
Indicates the ordinal position or identifying number assigned to a dynasty within a historical or genealogical sequence.
-
C.
dynasticStatus
chosen
Indicates the relationship between an entity and a ruling dynasty, such as membership in, association with, or status within that dynastic line.
-
D.
associatedDynasticOrder
Indicates a relationship where an entity is linked to, or formally connected with, a particular dynastic order.
-
E.
dynasticState
Indicates a relationship where a state or political entity is ruled or defined by a hereditary dynasty or ruling family.
- 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ddc66448190948280fb0c8d390c |
completed | April 16, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69deda7e6e748190b29ccce23298afef |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:09 a.m.