Triple
T22624980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iglesia Anglicana de Uruguay |
E558390
|
entity |
| Predicate | mainBodyFor |
P27808
|
FINISHED |
| Object | Anglican worship in Uruguay |
—
|
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: Anglican worship in Uruguay | Statement: [Iglesia Anglicana de Uruguay, mainBodyFor, Anglican worship in Uruguay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainBodyFor Context triple: [Iglesia Anglicana de Uruguay, mainBodyFor, Anglican worship in Uruguay]
-
A.
hasMainBody
Indicates that one entity serves as the primary physical or structural body of another entity.
-
B.
publicBody
Indicates that an entity functions as a governmental or publicly controlled organization that performs public duties or services.
-
C.
subBody
Indicates that one entity is a physical or conceptual sub-component or subsection of another entity’s body.
-
D.
mainBoardFor
Indicates that one entity serves as the primary circuit board or central board used by another entity.
-
E.
primaryBody
chosen
Indicates that one entity serves as the main or principal body associated with 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_69e24545a8e08190bfa7482a2c725ff1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f16e3c5cb88190b172f9f92eb58d7f |
completed | April 29, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 3:01 p.m.