Triple
T37984429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pagewood |
E947646
|
entity |
| Predicate | hasNearbyBeachSuburb |
P95431
|
FINISHED |
| Object | Maroubra Beach |
—
|
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: Maroubra Beach | Statement: [Pagewood, hasNearbyBeachSuburb, Maroubra Beach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyBeachSuburb Context triple: [Pagewood, hasNearbyBeachSuburb, Maroubra Beach]
-
A.
hasBeachNearby
chosen
Indicates that one location is situated close enough to another location to have convenient access to a beach.
-
B.
isCoastalProximitySuburbOf
Indicates that one suburb is located near the coast and is considered a suburban area associated with a particular primary locality or city.
-
C.
hasBeach
Indicates that one entity possesses, includes, or is characterized by a beach as part of its features or environment.
-
D.
isCoastalCitySuburb
Indicates that a suburb is located within or adjacent to a city that lies on a coastline, functioning as a suburban area of that coastal city.
-
E.
beachSubdivisionOf
Indicates that a beach is a component or sub-area of a larger geographic or administrative region.
- 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_69f76ef8a1d08190a741bbbc5970e3b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00b2b425a8819091ff65695e98c3af |
completed | May 10, 2026, 4:30 p.m. |
| PD | Predicate disambiguation | batch_6a00b06efa248190b2d16b4889185119 |
completed | May 10, 2026, 4:21 p.m. |
Created at: May 3, 2026, 4:20 p.m.