Triple
T24017592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jason Hervey |
E594724
|
entity |
| Predicate | siblingOnShow |
P47724
|
FINISHED |
| Object | Kevin Arnold |
—
|
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: Kevin Arnold | Statement: [Jason Hervey, siblingOnShow, Kevin Arnold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: siblingOnShow Context triple: [Jason Hervey, siblingOnShow, Kevin Arnold]
-
A.
onScreenSibling
chosen
Indicates that two characters are depicted as siblings within an on-screen or fictional context.
-
B.
sisterShow
Indicates that two shows are related as sister shows, typically sharing common origins, networks, or production ties without one being derived from the other.
-
C.
siblingBranch
Indicates that two branches share the same immediate parent node in a hierarchical structure, making them parallel or peer branches.
-
D.
siblingGroup
Indicates that multiple individuals belong to the same set of siblings, sharing at least one parent in common.
-
E.
hasSiblingSeriesAppearance
Indicates that two entities appear as siblings within the same series or narrative work.
- 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d5a6123c8190871e10cb81dfa819 |
completed | April 29, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:42 p.m.