Triple
T12839581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden Age Nursing Home fire |
E307011
|
entity |
| Predicate | occurredInBuildingType |
P1844
|
FINISHED |
| Object | nursing home |
—
|
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: nursing home | Statement: [Golden Age Nursing Home fire, occurredInBuildingType, nursing home]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occurredInBuildingType Context triple: [Golden Age Nursing Home fire, occurredInBuildingType, nursing home]
-
A.
containsBuildingType
Indicates that a location or area includes at least one building of the specified type.
-
B.
appliedToBuildingType
Indicates that something (such as a rule, measure, or classification) is specifically applicable to a particular type of building.
-
C.
belongsToBuildingType
Indicates that something is classified as being of a particular building type.
-
D.
buildingType
chosen
Indicates the specific category or function that characterizes what kind of building something is.
-
E.
originalBuildingType
Indicates the type or category of building that something was initially constructed or designated to be, before any later changes or repurposing.
- 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_69d7bdf52b94819096d6f0ba4ab50a98 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714208f881908f7f8a921362909a |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa08cd481909a946046ba63809f |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:35 p.m.