Triple
T37243462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop of Gallup |
E923778
|
entity |
| Predicate | overseesTerritoryIn |
P169368
|
FINISHED |
| Object | New Mexico |
—
|
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: New Mexico | Statement: [Bishop of Gallup, overseesTerritoryIn, New Mexico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overseesTerritoryIn Context triple: [Bishop of Gallup, overseesTerritoryIn, New Mexico]
-
A.
overseesTerritoryType
Indicates that an entity has supervisory or administrative responsibility over a specified type of territory.
-
B.
overTerritory
chosen
Indicates that one entity has control, authority, or dominance over a specific territory or geographic area in relation to another.
-
C.
oversawArea
Indicates that one entity had supervisory or managerial responsibility over a particular area, region, or domain associated with another entity.
-
D.
activeInTerritory
Indicates that an entity conducts operations, activities, or maintains a presence within a specified geographic territory.
-
E.
operatesFromTerritory
Indicates that an entity conducts its activities or operations based out of, or primarily within, a specified territory.
- 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_69f76ea9fee88190a589f661d95a7189 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:15 p.m.