Triple
T28566880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penny Hofstadter |
E722701
|
entity |
| Predicate | livesAcrossTheHallFrom |
P113241
|
FINISHED |
| Object | Leonard Hofstadter |
—
|
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: Leonard Hofstadter | Statement: [Penny Hofstadter, livesAcrossTheHallFrom, Leonard Hofstadter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: livesAcrossTheHallFrom Context triple: [Penny Hofstadter, livesAcrossTheHallFrom, Leonard Hofstadter]
-
A.
livesAcross
chosen
Indicates that one entity resides in a dwelling or location situated directly across from another entity’s dwelling or location, typically on the opposite side of a street or similar dividing space.
-
B.
livesUnder
Indicates that one entity resides beneath or is domiciled in a lower hierarchical or physical level relative to another entity.
-
C.
alsoLivesIn
Indicates that two or more entities share the same place of residence.
-
D.
residesNear
Indicates that one entity lives or is located in close physical proximity to another entity.
-
E.
neighborCharacter
Indicates that one character is located adjacent to or next to another character in a given context.
- 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_69f01a5f69d08190ad5c0d2167078dec |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6508f9be0819094d2968611578175 |
completed | May 2, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 4:07 a.m.