Triple
T11797164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kariocha |
E280529
|
entity |
| Predicate | resultsInStatus |
P38040
|
FINISHED |
| Object | priest of the orishas |
—
|
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: priest of the orishas | Statement: [Kariocha, resultsInStatus, priest of the orishas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultsInStatus Context triple: [Kariocha, resultsInStatus, priest of the orishas]
-
A.
obtainedStatus
chosen
Indicates that an entity has received or achieved a particular status or condition as a result of some process or event.
-
B.
TestStatus
Indicates the current outcome or state of a test, such as whether it has passed, failed, is in progress, or has not yet been executed.
-
C.
statusIncludes
Indicates that one entity’s status set contains or encompasses the status (or statuses) of another entity.
-
D.
resultsReleasedIn
Indicates that the results of an event, process, or evaluation were made publicly available in a specified location, medium, or context.
-
E.
submissionStatus
Indicates the current state or phase of a submitted item within a review or processing workflow.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5a1cda0819092d66a82fd882786 |
completed | April 10, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69d8a2491f048190853239bc05090bf4 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.