Triple
T238876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rastafari movement |
E4883
|
entity |
| Predicate | interpretsText |
P1044
|
FINISHED |
| Object | Bible in Afrocentric way |
—
|
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: Bible in Afrocentric way | Statement: [Rastafari movement, interpretsText, Bible in Afrocentric way]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interpretsText Context triple: [Rastafari movement, interpretsText, Bible in Afrocentric way]
-
A.
interpretedInCase
Indicates that something is understood, analyzed, or given meaning within the context of a particular case or specific situational scenario.
-
B.
interpretedAs
Indicates that something is understood, perceived, or taken to mean something else, often based on context or subjective judgment.
-
C.
isInterpretedBy
chosen
Indicates that something (such as data, a work, or a signal) is given meaning, understanding, or explanation by a particular agent or process.
-
D.
textType
Indicates the classification of a text according to its type, format, or genre.
-
E.
statuteInterpreted
Indicates that a legal authority (such as a court or agency) has provided an interpretation or authoritative reading of a particular statute.
- 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_69a257c3d0708190b0871c4269d273e6 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25dacf60c8190a5c3ef455b9a8b20 |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b5f27208190ae13f34037fe582b |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.