Triple
T34199573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O.B.G. |
E877337
|
entity |
| Predicate | indicatesReceiptOf |
P52361
|
FINISHED |
| Object | Order of the Baobab (Gold) |
—
|
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: Order of the Baobab (Gold) | Statement: [O.B.G., indicatesReceiptOf, Order of the Baobab (Gold)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indicatesReceiptOf Context triple: [O.B.G., indicatesReceiptOf, Order of the Baobab (Gold)]
-
A.
receivedSign
Indicates that one entity has obtained or been given a sign (such as a signal, symbol, or indication) from another entity.
-
B.
receivedTransmissionOf
Indicates that one entity has obtained or been sent a transmission (such as a message, signal, or data) originating from another entity.
-
C.
receivedIn
Indicates that something was obtained, accepted, or taken possession of within a particular context, location, or time frame.
-
D.
receivedFor
Indicates that something was obtained, accepted, or taken into possession on behalf of or for the benefit of a specified entity.
-
E.
recipientOf
chosen
Indicates that one entity is the receiver or beneficiary of something (such as an item, message, or action) from 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_69f349aff5f0819096275315abea5344 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7102baf8081908c23da0e99710d85 |
completed | May 3, 2026, 9:06 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.