Triple
T31543732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Greene |
E804815
|
entity |
| Predicate | notableRelativeWork |
P203535
|
FINISHED |
| Object | Bonanza |
E215343
|
NE 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: Bonanza | Statement: [Charles Greene, notableRelativeWork, Bonanza]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRelativeWork Context triple: [Charles Greene, notableRelativeWork, Bonanza]
-
A.
relativeNotableWork
chosen
Indicates that one entity is a notable work (such as a creation, publication, or production) specifically associated with or produced by another related entity.
-
B.
notableRelative
Indicates that an entity has a relative who is notable or well-known, specifying that familial relationship.
-
C.
notableFromWork
Indicates that an entity is notable or well-known specifically because of a particular work it created, contributed to, or is associated with.
-
D.
notableWork
Indicates that one entity is a significant or well-known work (such as a book, artwork, or creation) produced by another entity.
-
E.
notableWorkWith
Indicates a relationship where two or more entities are recognized for having collaborated on or been jointly associated with a significant work or project.
- F. None of above.
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_69f348d11a048190a65eb8384a3754ac |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b2d6281108190926f170507de3532 |
completed | June 11, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 10:07 p.m.