Triple
T14784046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Cates |
E347463
|
entity |
| Predicate | onScreenRelationship |
P83409
|
FINISHED |
| Object | reluctant partnership with Reggie Hammond |
—
|
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: reluctant partnership with Reggie Hammond | Statement: [Jack Cates, onScreenRelationship, reluctant partnership with Reggie Hammond]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onScreenRelationship Context triple: [Jack Cates, onScreenRelationship, reluctant partnership with Reggie Hammond]
-
A.
onScreenSibling
Indicates that two characters are depicted as siblings within an on-screen or fictional context.
-
B.
showsRelationshipWith
chosen
Indicates that one entity visually or explicitly presents or demonstrates its connection or association with another entity.
-
C.
onScreenSiblingActor
Indicates that two actors have portrayed siblings in the same on-screen production.
-
D.
hasOnScreenFamilyMember
Indicates that one entity appears on screen as a family member of another entity.
-
E.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deca9f1c9c8190a8b28ba0ddd3e2e3 |
completed | April 14, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69de8c090d1081909b5a9bf437499d6c |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.