Triple
T35255917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vicarius Urbis |
E1018229
|
entity |
| Predicate | traditionalHolderRank |
P7007
|
FINISHED |
| Object | Cardinal |
—
|
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: Cardinal | Statement: [Vicarius Urbis, traditionalHolderRank, Cardinal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalHolderRank Context triple: [Vicarius Urbis, traditionalHolderRank, Cardinal]
-
A.
lastHolderRank
Indicates the rank or position held by the most recent entity that possessed or held a given item, title, or role.
-
B.
titleHolderRank
Indicates the relative position or level of precedence assigned to a title holder within a ranked order or hierarchy.
-
C.
traditionallyRankedAfter
Indicates that one entity is customarily ordered or placed after another according to established tradition or conventional ranking.
-
D.
typicallyHoldsRank
chosen
Indicates that an entity is most commonly or usually associated with holding a particular rank or level in a hierarchy.
-
E.
chronRank
Indicates the relative chronological order or ranking of events or time-related entities with respect to one another.
- 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_69f76de407d081909dfc3c419817ae93 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff56ef0a5c8190ae729d66a8cf7fc4 |
completed | May 9, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ff539859c481909ec56310da418688 |
completed | May 9, 2026, 3:32 p.m. |
Created at: May 3, 2026, 4:02 p.m.