Triple
T10811543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander Sebastian |
E255111
|
entity |
| Predicate | relationshipToAliciaHuberman |
P95580
|
FINISHED |
| Object | husband |
—
|
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: husband | Statement: [Alexander Sebastian, relationshipToAliciaHuberman, husband]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToAliciaHuberman Context triple: [Alexander Sebastian, relationshipToAliciaHuberman, husband]
-
A.
relationshipTypeWith Alicia Johns
Indicates the specific type or nature of the relationship that an entity has with Alicia Johns.
-
B.
relationshipToJoannaKramer
Indicates the specific familial, social, or interpersonal connection that one entity has to Joanna Kramer.
-
C.
relationshipToEmmaGoldman
Indicates the specific type of personal, professional, or ideological relationship an entity has to Emma Goldman.
-
D.
relationshipWithHumbertHumbert
Indicates that an entity has a specified type of personal, emotional, or social relationship with Humbert Humbert.
-
E.
associationWithHumans
Indicates a general relationship, connection, or involvement between an entity and one or more humans.
- F. None of above. chosen
Provenance (4 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_69d6aa61c15c8190a1839550c56e75e1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d733b7bfac8190b6ae34144376d6ad |
completed | April 9, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69d6f3188f00819094ee8d65b187a333 |
completed | April 9, 2026, 12:30 a.m. |
| PDg | Predicate description generation | batch_69d6fa334b8c819082eaf8537084c323 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:18 p.m.