Triple
T34202450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitan Archbishop |
E877423
|
entity |
| Predicate | hasTerritorialSee |
P195783
|
FINISHED |
| Object | metropolitan see |
—
|
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: metropolitan see | Statement: [Metropolitan Archbishop, hasTerritorialSee, metropolitan see]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTerritorialSee Context triple: [Metropolitan Archbishop, hasTerritorialSee, metropolitan see]
-
A.
hasTerritorialAssociation
Indicates a relationship where an entity is linked or connected to a specific territory, area, or geographic region.
-
B.
hasTerritorialInterestIn
Indicates that an entity claims, seeks, or maintains control, influence, or rights over a specific geographic area or territory.
-
C.
hasTerritorialDimension
Indicates that something possesses or involves a spatial or territorial extent, scope, or jurisdiction.
-
D.
hasAncestralTerritoriesIn
Indicates that an entity traditionally holds or is associated with ancestral lands located within a specified geographic area.
-
E.
hasConstituentTerritory
Indicates that one geopolitical entity includes another as a territorial part or subdivision within its jurisdiction.
- 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_69f349aff5f0819096275315abea5344 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69fde5d677b88190bc904e6df8617c18 |
completed | May 8, 2026, 1:32 p.m. |
Created at: May 1, 2026, 1:55 a.m.