Triple
T6405874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ben Stokes |
E144175
|
entity |
| Predicate | honourReason |
P33845
|
FINISHED |
| Object | services to cricket |
—
|
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: services to cricket | Statement: [Ben Stokes, honourReason, services to cricket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honourReason Context triple: [Ben Stokes, honourReason, services to cricket]
-
A.
reasonForHonorific
chosen
Indicates the reason, justification, or basis for which an honorific title or form of address is granted to or used for an entity.
-
B.
honourOf
Indicates that one entity is the source, bearer, or cause of another entity’s honor, prestige, or distinguished recognition.
-
C.
honour
Indicates showing respect, admiration, or recognition toward someone or something, often through actions, words, or ceremonial acknowledgment.
-
D.
honourType
Indicates the specific category or classification of an honour or award associated with an entity.
-
E.
specialAwardReason
Indicates the specific reason or justification for which a special award is given to an 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_69c008dc56fc81908d43ffcc11d73bdd |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c068b22c74819092228010708aec6b |
completed | March 22, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69c060f40ecc8190b1df17b96767675c |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:35 p.m.