Triple
T24932413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fawkner |
E623221
|
entity |
| Predicate | cemeteryOpened |
P157248
|
FINISHED |
| Object | early 20th century (Fawkner Memorial Park) |
—
|
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: early 20th century (Fawkner Memorial Park) | Statement: [Fawkner, cemeteryOpened, early 20th century (Fawkner Memorial Park)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cemeteryOpened Context triple: [Fawkner, cemeteryOpened, early 20th century (Fawkner Memorial Park)]
-
A.
hasCemetery
Indicates that one entity possesses, contains, or includes a cemetery associated with it.
-
B.
cemeteryArea
Indicates that an area or region is designated, used, or recognized as a cemetery.
-
C.
hasNearbyCemetery
Indicates that one entity is located close to, or in the immediate vicinity of, a cemetery associated with another entity.
-
D.
cemeteryComplex
Indicates a relationship where a site or structure functions as, or is part of, a cemetery complex used for burials or memorials.
-
E.
isCemeteryFor
Indicates that one entity serves as the burial ground designated for another entity, such as a community, group, or location.
- 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_69e2fac6b5a48190a1c38857f00915a9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f423b581f4819095837c77f615658a |
completed | May 1, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69f4210130d08190ae30b7943f7a0bbc |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f423637bec8190a1701421ac86a3b7 |
completed | May 1, 2026, 3:52 a.m. |
Created at: April 18, 2026, 5:30 a.m.