Triple
T9122400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reed Dance |
E218885
|
entity |
| Predicate | involvesRecipient |
P14855
|
FINISHED |
| Object | Zulu monarch |
—
|
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: Zulu monarch | Statement: [Reed Dance, involvesRecipient, Zulu monarch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesRecipient Context triple: [Reed Dance, involvesRecipient, Zulu monarch]
-
A.
recipientOf
Indicates that one entity is the receiver or beneficiary of something (such as an item, message, or action) from another entity.
-
B.
individualRecipient
chosen
Indicates that a specific individual is the direct recipient or beneficiary of something (such as an item, message, or action).
-
C.
coRecipientWith
Indicates that two or more entities receive the same item, benefit, or communication together as joint recipients.
-
D.
notableRecipient
Indicates that an entity has received a notable award, honor, or recognition from another entity.
-
E.
notableRecipientType
Indicates that an entity is notably recognized as a recipient of something (such as an award, honor, or distinction) of a specified type.
- 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_69ca83dddd548190983b96c664f7f367 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8b46dac8190bde88205c85f596a |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc66003e3c819091e1e42c9cf7c781 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:17 p.m.