Triple
T30151481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pontifical Basilica |
E766407
|
entity |
| Predicate | hasJurisdictionalRelation |
P46880
|
FINISHED |
| Object | Holy See |
—
|
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: Holy See | Statement: [Pontifical Basilica, hasJurisdictionalRelation, Holy See]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJurisdictionalRelation Context triple: [Pontifical Basilica, hasJurisdictionalRelation, Holy See]
-
A.
hasJurisdictionOver
Indicates that one authority or governing body holds legal power or control to make and enforce decisions over another entity, area, or matter.
-
B.
hasAdjacentJurisdiction
Indicates that one jurisdiction directly borders or is immediately next to another jurisdiction.
-
C.
hasPoliticalJurisdictionType
Indicates the type or category of political jurisdiction that applies to or governs an entity.
-
D.
associatedWithJurisdiction
chosen
Indicates that an entity has a formal or relevant connection to a particular legal or administrative jurisdiction.
-
E.
hasJurisdictionOverlapWith
Indicates that two authorities or entities share some portion of legal or regulatory control over the same area, subject, or set of activities.
- 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_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ed4297c81909062f19b7795f181 |
completed | May 2, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:20 p.m.