Triple
T14583805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berkeley Vale |
E342260
|
entity |
| Predicate | hasAgedCareFacility |
P105
|
FINISHED |
| Object | various aged care homes |
—
|
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: various aged care homes | Statement: [Berkeley Vale, hasAgedCareFacility, various aged care homes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAgedCareFacility Context triple: [Berkeley Vale, hasAgedCareFacility, various aged care homes]
-
A.
agingFacility
Indicates that a facility is undergoing or associated with the process of aging, deterioration, or decline in condition over time.
-
B.
legacyFacilityOf
Indicates that one facility is an older, predecessor, or superseded version of another facility within the same organizational or operational context.
-
C.
homeFacilityName
Indicates the name of the primary facility or location that serves as the entity’s designated home base.
-
D.
hasNotableFacility
chosen
Indicates that an entity possesses or hosts a facility that is of particular significance, prominence, or interest.
-
E.
usesFacilityFor
Indicates that an entity makes use of a particular facility to carry out a specific purpose, activity, or function.
- 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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4209b988190ad2a7b2dead8ffed |
completed | April 14, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69de656a953481909a4645b004c40de7 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:24 a.m.