Triple
T18733223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buster Daniels |
E458090
|
entity |
| Predicate | hasNotableAchievementsDocumented |
P107335
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Buster Daniels, hasNotableAchievementsDocumented, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableAchievementsDocumented Context triple: [Buster Daniels, hasNotableAchievementsDocumented, no]
-
A.
hasNotableAchievements
Indicates that the subject possesses significant accomplishments, distinctions, or recognitions that are considered noteworthy.
-
B.
hasWidelyDocumentedPublicAchievements
chosen
Indicates that the subject has notable accomplishments that are extensively recorded and recognized in public sources.
-
C.
hasNotableWorkSection
Indicates that a notable work is associated with a specific section or part of a larger work or document.
-
D.
hasReferentNotableAchievement
Indicates that an entity’s referent is associated with a specific notable achievement or accomplishment.
-
E.
hasNotableRecognitionAs
Indicates that an entity has received notable recognition, distinction, or status specifically in the role, capacity, or identity denoted by the related 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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56d791ab88190b333503f9b1ad0c0 |
completed | April 20, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69e48d03766c8190a43f7681842f4f8d |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.