Triple
T12638538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moor Park |
E301828
|
entity |
| Predicate | hasSuburbCharacter |
P9847
|
FINISHED |
| Object | leafy residential area |
—
|
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: leafy residential area | Statement: [Moor Park, hasSuburbCharacter, leafy residential area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuburbCharacter Context triple: [Moor Park, hasSuburbCharacter, leafy residential area]
-
A.
hasSuburbanCharacter
chosen
Indicates that something possesses qualities or features typically associated with suburban areas, such as lower density, residential focus, and car-oriented development.
-
B.
hasSuburbAlong
Indicates that a larger area or route is associated with, or passes by, one or more suburbs located along its extent.
-
C.
containsSuburbs
Indicates that a larger geographic area or administrative region includes one or more suburbs within its boundaries.
-
D.
hasMajorSuburb
Indicates that a larger urban area includes or is associated with a specific major suburb within its boundaries or sphere.
-
E.
innerSuburbOf
Indicates that one location is a suburb situated within or forming part of a larger city or metropolitan area.
- 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_69d7bdec9f9c8190b4bac675b7588211 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960b47130819097e1162ed4fc993a |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:16 p.m.