Triple
T32339054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sozopolis in Pisidia |
E826257
|
entity |
| Predicate | titularSeeOf |
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: [Sozopolis in Pisidia, titularSeeOf, Roman Catholic Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titularSeeOf Context triple: [Sozopolis in Pisidia, titularSeeOf, Roman Catholic Church]
-
A.
isTitularSeeOf
chosen
Indicates that one ecclesiastical jurisdiction holds the honorary or formal status of being the titular see associated with another entity (such as a bishop or office).
-
B.
titularCharacterOf
Indicates that one entity is the main or title character featured in the work represented by the other entity.
-
C.
titleHolderSee
Indicates that one who holds a title or position observes, meets, or has an in-person encounter with another entity.
-
D.
titleHolderIs
Indicates that one entity currently holds or possesses a specific title associated with another entity.
-
E.
titleHolderName
Indicates the name of the person or entity that holds a particular title or position.
- 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_69f34913d9048190befaa634025232be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6be1f3a648190802496b36cf767f6 |
completed | May 3, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69f6b633e0c88190a727bb7d2751e2d5 |
completed | May 3, 2026, 2:43 a.m. |
Created at: May 1, 2026, 12:48 a.m.