Triple
T22219287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rees Jones |
E549164
|
entity |
| Predicate | notableNicknameReason |
P38200
|
FINISHED |
| Object | for his work preparing U.S. Open venues |
—
|
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: for his work preparing U.S. Open venues | Statement: [Rees Jones, notableNicknameReason, for his work preparing U.S. Open venues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableNicknameReason Context triple: [Rees Jones, notableNicknameReason, for his work preparing U.S. Open venues]
-
A.
notableNickname
Indicates that one entity is a well-known or widely recognized nickname or moniker for another entity.
-
B.
notablePlayNickname
Indicates that a particular play or performance is commonly known by a specific nickname.
-
C.
notableGameNickname
Indicates that an entity is a well-known or commonly used nickname for a particular game.
-
D.
nicknamedFor
chosen
Indicates that one entity serves as the source, inspiration, or reason for another entity’s nickname.
-
E.
namedPersonNotableFor
Indicates that a person is especially known or recognized for a particular work, role, achievement, or characteristic.
- 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_69e11e403d6481909a94d0aaf157f6ef |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b8edd288190a49f10e009122057 |
completed | April 28, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69e71b4dcc408190a30429fb08fcf39e |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:37 p.m.