Triple
T32849157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ludovico Ludovisi |
E840194
|
entity |
| Predicate | titleOfCardinal |
P101310
|
FINISHED |
| Object | Cardinal-Priest of Santa Maria in Traspontina |
—
|
NE NERFINISHED |
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-Priest of Santa Maria in Traspontina | Statement: [Ludovico Ludovisi, titleOfCardinal, Cardinal-Priest of Santa Maria in Traspontina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleOfCardinal Context triple: [Ludovico Ludovisi, titleOfCardinal, Cardinal-Priest of Santa Maria in Traspontina]
-
A.
cardinalName
Indicates that an entity has a specific cardinal (numerical order) name or label.
-
B.
cardinalateTitle
chosen
Indicates the specific cardinal rank or title conferred on a person within the College of Cardinals.
-
C.
typeOfCardinal
Indicates a classification relationship where one entity is a specific kind or subtype of a broader cardinal category represented by the other entity.
-
D.
createdCardinalOf
Indicates that an entity established or founded the position or office of a cardinal for another entity.
-
E.
titleInRomanNumerals
Indicates that an entity’s title is expressed or represented using Roman numerals.
- 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_69f349412c78819084459850e11d29f7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fedec693b08190b0f8bfdb921e0766 |
completed | May 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69fede16c1d48190a20d8a9c5722c307 |
completed | May 9, 2026, 7:11 a.m. |
Created at: May 1, 2026, 1:17 a.m.