Triple
T37003436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "The Plums" stories |
E915417
|
entity |
| Predicate | inUniverseFamilyResidence |
P136761
|
FINISHED |
| Object | large house in St. Louis |
—
|
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: large house in St. Louis | Statement: ["The Plums" stories, inUniverseFamilyResidence, large house in St. Louis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseFamilyResidence Context triple: ["The Plums" stories, inUniverseFamilyResidence, large house in St. Louis]
-
A.
inResidenceAt
Indicates that an entity lives or resides at a particular location or residence.
-
B.
hasRulingFamilyResidence
chosen
Indicates that a location serves as the primary home or official residence of a ruling family.
-
C.
residesUnder
Indicates that one entity lives or is situated beneath another entity in a hierarchical or spatial structure.
-
D.
hostResidenceOf
Indicates that a location serves as the primary place of residence for a specified person or group.
-
E.
hasResidenceIn
Indicates that an entity lives or maintains a primary dwelling in a specified location.
- 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: May 3, 2026, 4:14 p.m.