Triple
T7905541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gary Oldman as Tiny Tim |
E183565
|
entity |
| Predicate | familyRelationInStory |
P38921
|
FINISHED |
| Object | son of Bob Cratchit |
—
|
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: son of Bob Cratchit | Statement: [Gary Oldman as Tiny Tim, familyRelationInStory, son of Bob Cratchit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyRelationInStory Context triple: [Gary Oldman as Tiny Tim, familyRelationInStory, son of Bob Cratchit]
-
A.
fictionalRelationship
Indicates a relationship that exists only within a fictional or imagined context between entities.
-
B.
relationshipToCharacter
chosen
Indicates the specific type of personal, social, or narrative connection that one entity has to a given character.
-
C.
playerRelations
Indicates the nature or status of the relationship between players, such as alliances, rivalries, or other interpersonal dynamics.
-
D.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
E.
familyAspect
Indicates a relationship where one entity is characterized by a particular familial role, status, or aspect in relation to another entity.
- 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_69ca828d13088190b222be7aa9f9315c |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a56c9f0819094dc87fe55a8823e |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae92f9498819085277879e59aa072 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:03 p.m.