Triple
T34255196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Ubriacco |
E878857
|
entity |
| Predicate | hasOnScreenChildRelationshipWith |
P185980
|
FINISHED |
| Object | Mikey |
—
|
NE NERFINISHED |
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: Mikey | Statement: [James Ubriacco, hasOnScreenChildRelationshipWith, Mikey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnScreenChildRelationshipWith Context triple: [James Ubriacco, hasOnScreenChildRelationshipWith, Mikey]
-
A.
onScreenSibling
Indicates that two characters are depicted as siblings within an on-screen or fictional context.
-
B.
hasOnScreenSonWith
chosen
Indicates that two entities are related such that one appears as the on-screen son of the other in a visual media context.
-
C.
hasChildIn
Indicates that one entity has a child who is located in, associated with, or present within another specified entity or context.
-
D.
isChildIn
Indicates that one entity is the child (offspring or subordinate in a family or hierarchical structure) of another entity.
-
E.
hasOnScreenRelative
Indicates that one entity has a family member who appears or is depicted on screen in relation to it.
- 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_69f349b421cc8190b4b4655e1d612548 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 1, 2026, 1:56 a.m.