Triple
T24952595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burnley, Victoria |
E624378
|
entity |
| Predicate | planningZone |
P60867
|
FINISHED |
| Object | public parkland |
—
|
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: public parkland | Statement: [Burnley, Victoria, planningZone, public parkland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planningZone Context triple: [Burnley, Victoria, planningZone, public parkland]
-
A.
plannedArea
chosen
Indicates that an area is designated or intended for a specific planned use or development.
-
B.
partOfPlanningRegion
Indicates that one entity is included within, or belongs to, a larger designated planning region.
-
C.
plannedCompetitionZone
Indicates that a specific area has been designated in advance as the location where a competition or contest is intended to take place.
-
D.
regionTypePlanned
Indicates that a region is intended or designated to have a specific type or classification in a planned or future state.
-
E.
planning
Indicates that an entity is engaged in organizing or devising a future action, event, or course of behavior involving another entity or entities.
- 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_69e2ff22e4c48190a0444b5a044f14e8 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 5:57 a.m.