Triple
T14235480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olivia Crain |
E352864
|
entity |
| Predicate | relationshipToHouse |
P26313
|
FINISHED |
| Object | psychically sensitive to Hill House |
—
|
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: psychically sensitive to Hill House | Statement: [Olivia Crain, relationshipToHouse, psychically sensitive to Hill House]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToHouse Context triple: [Olivia Crain, relationshipToHouse, psychically sensitive to Hill House]
-
A.
relationshipBetweenHouses
Indicates a relational connection or association that exists between two or more houses.
-
B.
associatedHouse
chosen
Indicates a relationship where one entity is linked or connected to a particular house, typically as its related or corresponding house.
-
C.
relationToMLS
Indicates a relationship or association that an entity has with a specific MLS (Multiple Listing Service) system or record.
-
D.
relationshipToHumans
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
-
E.
houseOrFamily
Indicates that two entities are related through a shared house, household, or family membership.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de62411c888190a154acd56fe3fcaf |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:07 a.m.