Triple
T28698264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doddie Weir Cup |
E729473
|
entity |
| Predicate | notablePersonHonoured |
P3737
|
FINISHED |
| Object | Scottish lock Doddie Weir |
—
|
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: Scottish lock Doddie Weir | Statement: [Doddie Weir Cup, notablePersonHonoured, Scottish lock Doddie Weir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePersonHonoured Context triple: [Doddie Weir Cup, notablePersonHonoured, Scottish lock Doddie Weir]
-
A.
honoredPerson
Indicates that a person is the recipient of honor, recognition, or special distinction from another party or in a particular context.
-
B.
notableAwardOrHonor
Indicates that an entity has received a specific notable award or honor.
-
C.
namedForNotabilityOfHonoree
Indicates that something is named in recognition of the honoree’s notable achievements, status, or significance.
-
D.
hasNotableHonoree
chosen
Indicates that an entity is notably dedicated to, named after, or honors a particular person or group.
-
E.
notableAwardRecognition
Indicates that an entity has received or been formally recognized with a notable award or honor.
- 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_69f043e6e9688190b6bdd6e5665498ff |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_6a0164b052608190adc93240dad50a06 |
completed | May 11, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_6a01637fd3ac8190970eb09650d1e659 |
completed | May 11, 2026, 5:05 a.m. |
Created at: April 28, 2026, 5:40 a.m.