Triple
T4825513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sophie Hopkins |
E107813
|
entity |
| Predicate | characterInNotableWork |
P55029
|
FINISHED |
| Object | April MacLean in Class |
—
|
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: April MacLean in Class | Statement: [Sophie Hopkins, characterInNotableWork, April MacLean in Class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterInNotableWork Context triple: [Sophie Hopkins, characterInNotableWork, April MacLean in Class]
-
A.
notableWorkRole
Indicates that a person’s role or position is specifically associated with the creation, performance, or contribution to a notable work.
-
B.
genreOfWorkCharacterIsIn
Indicates the specific genre of the creative work in which a given character appears.
-
C.
hasFictionalWork
Indicates that one entity is the creator, owner, or source of a fictional work associated with another entity.
-
D.
namedForNotableWork
Indicates that one entity is named in honor of another entity’s notable work or achievement.
-
E.
notableAppearanceIn
chosen
Indicates that an entity is prominently featured or plays a significant role in a particular work, event, or context.
- 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_69bd43fac8188190803f0327190621e4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1fe130819087ae01309f96a0c8 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:24 p.m.