Triple
T13587752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apostolic Majesty |
E324612
|
entity |
| Predicate | isHereditaryStyle |
P92835
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Apostolic Majesty, isHereditaryStyle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHereditaryStyle Context triple: [Apostolic Majesty, isHereditaryStyle, true]
-
A.
titleIsHereditary
Indicates that a title or rank is passed down through family lineage rather than being newly granted or earned each time.
-
B.
hasHereditaryDesignation
chosen
Indicates that an entity possesses a title, status, or designation that is passed down through family lineage or inheritance.
-
C.
hasHereditaryChief
Indicates that an entity is led or governed by a chief whose position is inherited through family lineage.
-
D.
hasTypeOfHeritage
Indicates that an entity is associated with a specific category or classification of heritage (such as cultural, natural, or historical heritage).
-
E.
hereditaryInFamily
Indicates that a trait, condition, or characteristic is passed down through generations within the same 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb054c6008190839384ce26e8f71a |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.