Triple
T25242362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aykah |
E632501
|
entity |
| Predicate | receivedMessenger |
P113861
|
FINISHED |
| Object | Shu'ayb |
—
|
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: Shu'ayb | Statement: [Aykah, receivedMessenger, Shu'ayb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedMessenger Context triple: [Aykah, receivedMessenger, Shu'ayb]
-
A.
receivedTransmissionOf
chosen
Indicates that one entity has obtained or been sent a transmission (such as a message, signal, or data) originating from another entity.
-
B.
receivedIn
Indicates that something was obtained, accepted, or taken possession of within a particular context, location, or time frame.
-
C.
receivedSign
Indicates that one entity has obtained or been given a sign (such as a signal, symbol, or indication) from another entity.
-
D.
receivedPromiseAbout
Indicates that one entity has been given an assurance or commitment concerning another entity or event by some source.
-
E.
receivedFor
Indicates that something was obtained, accepted, or taken into possession on behalf of or for the benefit of a specified 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 21, 2026, 1:08 p.m.