Triple
T31197651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princeps Pedemontii |
E795364
|
entity |
| Predicate | traditionalBearerRole |
P75765
|
FINISHED |
| Object | heir apparent |
—
|
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: heir apparent | Statement: [Princeps Pedemontii, traditionalBearerRole, heir apparent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalBearerRole Context triple: [Princeps Pedemontii, traditionalBearerRole, heir apparent]
-
A.
recognizedRole
Indicates that one entity acknowledges or accepts another entity’s role, position, or function within a given context.
-
B.
associatedWithRoleOfNameBearer
chosen
Indicates that an entity is connected to or involved with the specific role or function held by a designated name bearer.
-
C.
canonicalRole
Indicates that an entity holds a standard, primary, or officially recognized role within a particular context or system.
-
D.
eraOfBearer
Indicates that a time period or era is associated with, or characterizes, the bearer entity.
-
E.
formerBearer
Indicates that an entity previously held or carried something (such as a title, role, or object) but no longer does so.
- 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_69f224d7a6a481908187c4362a8a525f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
Created at: April 29, 2026, 9:09 p.m.