Triple
T14695648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cardinal-Bishop of Ostia e Velletri |
E345148
|
entity |
| Predicate | isOfficeFor |
P106060
|
FINISHED |
| Object | cardinal of episcopal order |
—
|
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 of episcopal order | Statement: [Cardinal-Bishop of Ostia e Velletri, isOfficeFor, cardinal of episcopal order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOfficeFor Context triple: [Cardinal-Bishop of Ostia e Velletri, isOfficeFor, cardinal of episcopal order]
-
A.
hasOffice
Indicates that an entity possesses or maintains an office at a particular location or within a specific organization.
-
B.
isOfficialOfficeOf
chosen
Indicates that one entity serves as the formally recognized office or headquarters associated with another entity.
-
C.
representsInOffice
Indicates that one entity serves as an official representative of another entity within a specific office, position, or institutional role.
-
D.
servesAsOfficeOf
Indicates that one entity functions as the official office, headquarters, or administrative base for another entity.
-
E.
hasOfficeType
Indicates that an entity’s office is classified as a specific type or category of office.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb58855e081908b38f9515db5677f |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de657c57ec8190ae0b9bb79a514566 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.