Triple
T19765613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Pope Paul V |
E474744
|
entity |
| Predicate | successorFamilyUse |
P137239
|
FINISHED |
| Object | Borghese family heraldry |
—
|
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: Borghese family heraldry | Statement: [Coat of arms of Pope Paul V, successorFamilyUse, Borghese family heraldry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorFamilyUse Context triple: [Coat of arms of Pope Paul V, successorFamilyUse, Borghese family heraldry]
-
A.
successorFamily
Indicates that one family succeeds or follows another family in a lineage, role, position, or ownership.
-
B.
successorUse
Indicates that one entity is used or applied as the subsequent or follow-up use of another entity in a sequence or lifecycle.
-
C.
usedByFamilyOf
Indicates that something is utilized or consumed by members of a particular family or household.
-
D.
usedByFamily
Indicates that something is regularly utilized or consumed by a family as a group.
-
E.
successorUsedIn
Indicates that a successor entity is utilized or referenced within the context, operation, or implementation of another entity.
- F. None of above. chosen
Provenance (4 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e653226af081909992ff5568bb54a5 |
completed | April 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:48 p.m.