Triple
T30462031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leptiminus |
E775038
|
entity |
| Predicate | isTitularSeeOf |
P169775
|
FINISHED |
| Object | Roman Catholic Church |
—
|
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: Roman Catholic Church | Statement: [Leptiminus, isTitularSeeOf, Roman Catholic Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTitularSeeOf Context triple: [Leptiminus, isTitularSeeOf, Roman Catholic Church]
-
A.
titularCharacterOf
Indicates that one entity is the main or title character featured in the work represented by the other entity.
-
B.
titleHolderBelongsTo
Indicates that the holder of a title is associated with or belongs to a particular entity, such as an organization, position, or domain.
-
C.
isShareholderOf
Indicates that one entity owns shares or equity in another entity, giving it a financial stake and certain associated rights in that entity.
-
D.
titleHolderSee
Indicates that one who holds a title or position observes, meets, or has an in-person encounter with another entity.
-
E.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f686f0d838819099ca4d828a246d7f |
completed | May 2, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f7e116c819099aec724e9ef3763 |
completed | May 2, 2026, 10:49 p.m. |
Created at: April 29, 2026, 8:10 p.m.