Triple
T36921303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juliette Silverton |
E913205
|
entity |
| Predicate | relationshipWithNick |
P132379
|
FINISHED |
| Object | strained after she becomes a Hexenbiest |
—
|
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: strained after she becomes a Hexenbiest | Statement: [Juliette Silverton, relationshipWithNick, strained after she becomes a Hexenbiest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipWithNick Context triple: [Juliette Silverton, relationshipWithNick, strained after she becomes a Hexenbiest]
-
A.
relationshipToNicholas
Indicates the specific familial, social, or professional relationship that one entity has to Nicholas.
-
B.
relationshipToNicole
Indicates the specific type of relationship or connection that an entity has with Nicole.
-
C.
relationshipTypeWithNickWells
chosen
Indicates the specific nature or category of relationship that an entity has with Nick Wells.
-
D.
relationshipToNina
Indicates that one entity has a specified personal or social relationship to Nina.
-
E.
relationshipToMike
Indicates the specific type of personal, social, or familial relationship that an entity has with Mike.
- 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_69f76e885b848190bad82c87e9525486 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.