Triple
T5965562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglicanism |
E132742
|
entity |
| Predicate | usesPrimaryLanguage |
P4185
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Anglicanism, usesPrimaryLanguage, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPrimaryLanguage Context triple: [Anglicanism, usesPrimaryLanguage, English]
-
A.
primaryLanguageOf
Indicates that a specified language is the main or official language used by a particular entity (such as a person, organization, or region).
-
B.
parentLanguage
Indicates that one language is the ancestral or source language from which another language is derived or historically developed.
-
C.
isLanguageOf
chosen
Indicates that a particular language is used as the official or primary language associated with a given entity (such as a person, document, or region).
-
D.
usesLanguageFamily
Indicates that an entity communicates or operates using a language that belongs to a specified language family.
-
E.
usesWorkingLanguagesOf
Indicates that one entity employs or operates using the working languages 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_69c0086c2364819091e9fe2f58fa2517 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03fb7f8a88190a8bd45208bda4a03 |
completed | March 22, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69c0335a635881909c58c1ef0f97f1e8 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4:03 p.m.