Triple
T28153189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TR35 award |
E714675
|
entity |
| Predicate | notablePastRecipient |
P37447
|
FINISHED |
| Object | Sergey Brin |
—
|
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: Sergey Brin | Statement: [TR35 award, notablePastRecipient, Sergey Brin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePastRecipient Context triple: [TR35 award, notablePastRecipient, Sergey Brin]
-
A.
notableFieldOfRecipients
Indicates that the recipients are notable or recognized specifically in a particular field or area of expertise.
-
B.
notableLaureatesInclude
chosen
Indicates that a group, institution, or award has among its distinguished recipients or members certain specified laureates.
-
C.
hasNotableHonoree
Indicates that an entity is notably dedicated to, named after, or honors a particular person or group.
-
D.
notableAwardedFor
Indicates that an award is notable specifically for being given in recognition of a particular work, achievement, or contribution.
-
E.
notableAchiever
Indicates that an entity has achieved notable success, distinction, or recognition in a particular field or domain.
- 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_69efd6b033208190bf74f80a147e2092 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_6a008d6085508190a71c52cd028a6297 |
completed | May 10, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_6a008ced31448190b8fc60bf87b40647 |
completed | May 10, 2026, 1:49 p.m. |
Created at: April 27, 2026, 10 p.m.