Triple
T10775057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Catholic Archdiocese of Rabat |
E254175
|
entity |
| Predicate | missionaryTerritory |
P94456
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Roman Catholic Archdiocese of Rabat, missionaryTerritory, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionaryTerritory Context triple: [Roman Catholic Archdiocese of Rabat, missionaryTerritory, yes]
-
A.
missionTerritoryOf
chosen
Indicates that a specified territory is under the jurisdiction or scope of a particular mission.
-
B.
federalTerritory
Indicates that one entity is designated as a federal territory under the jurisdiction or authority of another (typically a federal government or state).
-
C.
borderingStateOrTerritory
Indicates that one state or territory shares a common boundary with another state or territory.
-
D.
governedTerritory
Indicates that one entity exercises political authority or control over another entity or geographic area as its governing power.
-
E.
countryCedingTerritory
Indicates that one country is formally transferring control or ownership of a portion of its territory to another entity.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7329cc6c881908f827edff941d456 |
completed | April 9, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69d6f31455648190b5c24690487b1b54 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:16 p.m.