Triple
T28450011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Collingwood |
E716548
|
entity |
| Predicate | MBEFor |
P164735
|
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: [Paul Collingwood, MBEFor, Services to cricket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MBEFor Context triple: [Paul Collingwood, MBEFor, Services to cricket]
-
A.
mbege
Indicates a marital or spousal relationship between two entities.
-
B.
BCPFor
Indicates that something serves as the Business Continuity Plan (BCP) designated for a particular entity, process, or context.
-
C.
enactedFor
Indicates that an action, rule, or measure is formally established or put into effect on behalf of, or for the benefit of, a particular entity or group.
-
D.
boundFor
Indicates that something is destined, directed, or scheduled to go toward a particular destination or target.
-
E.
supremeBodyFor
Indicates that one entity serves as the highest authoritative body or ultimate governing authority for another entity.
- F. None of above. chosen
Provenance (4 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_69efd6b76f8c8190a7ba908aca280942 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f64ee0c2788190a94a04ad1902fd5e |
completed | May 2, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64e36c57c8190af09470a8d35512b |
completed | May 2, 2026, 7:19 p.m. |
Created at: April 28, 2026, 1:51 a.m.