Triple
T18260796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard Griffiths as Uncle Monty |
E437347
|
entity |
| Predicate | actorKnownFor |
P131071
|
FINISHED |
| Object | characterActing |
—
|
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: characterActing | Statement: [Richard Griffiths as Uncle Monty, actorKnownFor, characterActing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actorKnownFor Context triple: [Richard Griffiths as Uncle Monty, actorKnownFor, characterActing]
-
A.
laterKnownFor
Indicates that an entity became recognized or notable for something at a later time than the context or event currently being referred to.
-
B.
alsoKnownFor
Indicates that an entity is additionally recognized or noted for another work, role, achievement, or characteristic beyond its primary association.
-
C.
knownForAct
Indicates that an entity is recognized or notable for performing a particular act or action.
-
D.
creatorKnownFor
Indicates that a creator is especially recognized or notable for a particular work, contribution, or achievement.
-
E.
composerKnownFor
Indicates that a composer is particularly recognized or notable for a specific work, style, or contribution.
- F. None of above. chosen
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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ff7591b4819083f2b29d60298747 |
completed | April 19, 2026, 4:14 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:34 a.m.