Triple
T701190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apostolic Vicariate |
E14001
|
entity |
| Predicate | hasCanonicalNature |
P2435
|
FINISHED |
| Object | missionary circumscription |
—
|
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: missionary circumscription | Statement: [Apostolic Vicariate, hasCanonicalNature, missionary circumscription]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanonicalNature Context triple: [Apostolic Vicariate, hasCanonicalNature, missionary circumscription]
-
A.
hasCanonicalReference
Indicates that one entity serves as the authoritative or standard reference source for another entity.
-
B.
hasNature
chosen
Indicates that something possesses, exhibits, or is characterized by a particular inherent quality, essence, or fundamental type.
-
C.
hasClosedCanon
Indicates that a body of authoritative texts is considered complete and no additional works can be added to it.
-
D.
hasCanonicalNumberOfHeads
Indicates that an entity possesses the standard or officially recognized number of heads for its kind.
-
E.
isCanonicalZone
Indicates that a given zone is the primary, standard, or officially recognized version among possible alternatives.
- 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_69a493494ec48190ae6751683625a9ba |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a544e3608190ac315c7aa9f88e7e |
completed | March 1, 2026, 8:44 p.m. |
| PD | Predicate disambiguation | batch_69a4a4ec8c748190b198492a0eea4445 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:36 p.m.