Triple
T35566328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marleston |
E1027784
|
entity |
| Predicate | neighboringSuburbSoutheast |
P183412
|
FINISHED |
| Object | Everard Park |
—
|
NE NERFINISHED |
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: Everard Park | Statement: [Marleston, neighboringSuburbSoutheast, Everard Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neighboringSuburbSoutheast Context triple: [Marleston, neighboringSuburbSoutheast, Everard Park]
-
A.
neighboringSuburbEast
Indicates that one suburb is directly to the east of, and adjacent to, another suburb.
-
B.
neighboringSuburbSouth
Indicates that one suburb is directly to the south of, and adjacent to, another suburb.
-
C.
neighboringSuburbNortheast
Indicates that one suburb is located directly to the northeast of another, sharing a neighboring boundary in that direction.
-
D.
neighboringSuburbNorth
Indicates that one suburb is directly to the north of, and adjacent to, another suburb.
-
E.
isSuburbanNeighborhoodOf
Indicates that one area is a residential neighborhood located within or characteristic of the suburbs of another, typically larger, urban area.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f7340e4819092a1a47f7028e63f |
completed | May 3, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79ec14ce08190b22cee0b40d33743 |
completed | May 3, 2026, 7:15 p.m. |
Created at: May 3, 2026, 4:04 p.m.