Triple
T28947839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arab Armenia |
E730927
|
entity |
| Predicate | majorLocalReligion |
P109600
|
FINISHED |
| Object | Armenian Apostolic Church |
—
|
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: Armenian Apostolic Church | Statement: [Arab Armenia, majorLocalReligion, Armenian Apostolic Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorLocalReligion Context triple: [Arab Armenia, majorLocalReligion, Armenian Apostolic Church]
-
A.
localReligion
chosen
Indicates that a particular religion is practiced or holds significance within a specific local area or community.
-
B.
majorRegionOfWorship
Indicates the primary geographic region where a deity, religion, or cult is predominantly worshipped.
-
C.
traditionalReligionPlace
Indicates that a place is traditionally associated with the practice, worship, or activities of a particular religion.
-
D.
hostReligion
Indicates that an entity organizes, accommodates, or provides a venue for a particular religious group, event, or practice.
-
E.
majorReligionCanBe
Indicates that an entity can have a particular major religion as one of its possible primary religious affiliations.
- 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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: April 28, 2026, 8:41 a.m.