Triple
T27090711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Good Son |
E686158
|
entity |
| Predicate | showsLivingArrangement |
P105495
|
FINISHED |
| Object | Frasier living with Martin |
—
|
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: Frasier living with Martin | Statement: [The Good Son, showsLivingArrangement, Frasier living with Martin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showsLivingArrangement Context triple: [The Good Son, showsLivingArrangement, Frasier living with Martin]
-
A.
hasHousingArrangement
chosen
Indicates that an entity has a specific type or status of housing or living arrangement in relation to another entity or context.
-
B.
livesUnder
Indicates that one entity resides beneath or is domiciled in a lower hierarchical or physical level relative to another entity.
-
C.
depictsResidence
Indicates that one entity visually represents or portrays the place where another entity lives or resides.
-
D.
residenceType
Indicates the kind or category of dwelling or living arrangement associated with an entity.
-
E.
housingPattern
Indicates the typical arrangement or distribution of housing units or residential structures within a given area or 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f62349888081908305958558907967 |
completed | May 2, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 8:40 a.m.