Triple
T33266727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harrell Harris |
E851668
|
entity |
| Predicate | creativeWorkRelation |
P111975
|
FINISHED |
| Object | Ego persona |
—
|
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: Ego persona | Statement: [Harrell Harris, creativeWorkRelation, Ego persona]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creativeWorkRelation Context triple: [Harrell Harris, creativeWorkRelation, Ego persona]
-
A.
hasRelationToOtherWork
Indicates that one work bears a specified relationship (such as adaptation, sequel, reference, or influence) to another distinct work.
-
B.
relatedToAuthorWork
chosen
Indicates that there is a connection or association between an author and a work they have created, contributed to, or are otherwise linked with.
-
C.
starringInRelatedWork
Indicates that an entity appears as a star or lead performer in a work that is related to another primary work or context.
-
D.
associatedActOfCreator
Indicates a relationship where an act is linked to the creator responsible for or connected with that act.
-
E.
creatorOfWorkAppearedIn
Indicates that a person is the creator (e.g., author, artist, director) of a work in which a given entity appeared.
- 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff136ed2a881908f713401083970d1 |
completed | May 9, 2026, 10:58 a.m. |
| PD | Predicate disambiguation | batch_69ff10f9e3448190b6cb6ea5a67713c1 |
completed | May 9, 2026, 10:48 a.m. |
Created at: May 1, 2026, 1:32 a.m.