Triple
T9723277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarah Altman |
E235534
|
entity |
| Predicate | homeFeature |
P90668
|
FINISHED |
| Object | fortified safe room |
—
|
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: fortified safe room | Statement: [Sarah Altman, homeFeature, fortified safe room]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeFeature Context triple: [Sarah Altman, homeFeature, fortified safe room]
-
A.
homeFunction
Indicates that something serves as the primary place where an entity lives, resides, or is based.
-
B.
homeTo
Indicates that a place serves as the primary location, residence, or habitat for a person, group, or thing.
-
C.
homeSection
Indicates that something belongs to, is part of, or is designated as the primary/home section within a larger structure or collection.
-
D.
homeManager
Indicates that one entity manages, oversees, or is responsible for the operations or affairs of another entity’s home or household.
-
E.
homeGroundFeature
Indicates that a particular feature or characteristic is associated with or defines the home ground of an entity.
- 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_69ca84d0123c819096f9dc3b6abb0881 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9e75abd48190a6e6679ec51496e8 |
completed | April 1, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69cd03c6ffc88190a5e9569e19122ad5 |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd07c5c978819084abc7267a5ced80 |
completed | April 1, 2026, 11:55 a.m. |
Created at: March 30, 2026, 8:20 p.m.