Triple
T30776623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jess and Jason |
E783690
|
entity |
| Predicate | actualNamesOfCharacters |
P155411
|
FINISHED |
| Object | Megan Hipwell and Scott Hipwell |
—
|
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: Megan Hipwell and Scott Hipwell | Statement: [Jess and Jason, actualNamesOfCharacters, Megan Hipwell and Scott Hipwell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actualNamesOfCharacters Context triple: [Jess and Jason, actualNamesOfCharacters, Megan Hipwell and Scott Hipwell]
-
A.
titleCharacterRealName
chosen
Indicates that a character known by a title or alias has the specified real (personal) name.
-
B.
characterFullName
Indicates that the predicate specifies the complete, formal name of a character.
-
C.
associatedCharacters
Indicates that two or more characters are linked or connected through some relationship, involvement, or relevance to each other.
-
D.
hasCharacterNamedAfter
Indicates that one entity has a character whose name is derived from or intentionally based on another entity.
-
E.
titleCharacterNamedAfter
Indicates that a work’s title character is named after, or shares their name with, another specific 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68fe1c4d881908f331699d11a3c3f |
completed | May 2, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:41 p.m.