Triple
T33210695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rick Dockery |
E850148
|
entity |
| Predicate | basedInWorkOnRealPerson |
P93832
|
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: [Rick Dockery, basedInWorkOnRealPerson, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedInWorkOnRealPerson Context triple: [Rick Dockery, basedInWorkOnRealPerson, no]
-
A.
basedOnRealPersonFor
Indicates that one entity is created, modeled, or inspired using a specific real person as its basis.
-
B.
realPerson
Indicates that the referenced entity corresponds to an actual human individual, as opposed to a fictional, anonymous, or non-human entity.
-
C.
basedOnRealLife
chosen
Indicates that something is derived from, inspired by, or directly adapted from actual real-world events, people, or situations.
-
D.
workBasedOnThisCharacter
Indicates that a creative work is based on, inspired by, or derived from the referenced character.
-
E.
featuresRealPersonAsHimself
Indicates that a real person appears in the work portraying themself rather than a fictional character.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fea5e828cc8190a9b755a645dc56d2 |
completed | May 9, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69fea36443f08190b2aced9b4a0525fd |
completed | May 9, 2026, 3 a.m. |
Created at: May 1, 2026, 1:30 a.m.