Triple
T35788884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bahá'í administration |
E1034633
|
entity |
| Predicate | globalBody |
P173932
|
FINISHED |
| Object | Universal House of Justice |
—
|
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: Universal House of Justice | Statement: [Bahá'í administration, globalBody, Universal House of Justice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: globalBody Context triple: [Bahá'í administration, globalBody, Universal House of Justice]
-
A.
publicBody
Indicates that an entity functions as a governmental or publicly controlled organization that performs public duties or services.
-
B.
oreBody
Indicates that one entity is an ore body, i.e., a naturally occurring concentration of minerals in the context of the other entity.
-
C.
isGlobalBodyOf
chosen
Indicates that one entity functions as the overarching, worldwide governing or coordinating body for another entity or domain.
-
D.
definedBody
Indicates that one entity serves as the formal specification, content, or body definition of another entity.
-
E.
targetsBody
Indicates that one entity is directed at, aimed at, or focused on affecting the body of 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a22cd75c81909c3a721b69f8b9a5 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.