Triple
T15409838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurstville |
E368556
|
entity |
| Predicate | isMajorResidentialArea |
P62289
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Hurstville, isMajorResidentialArea, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorResidentialArea Context triple: [Hurstville, isMajorResidentialArea, true]
-
A.
isSuburbanResidentialArea
chosen
Indicates that a location is primarily a residential neighborhood situated in a suburban (non-urban, non-rural) setting.
-
B.
hasResidentialArea
Indicates that an entity includes, contains, or is associated with an area designated for people to live or reside.
-
C.
isResidentialTown
Indicates that a town is primarily used or designated for residential living rather than for commercial, industrial, or other primary purposes.
-
D.
isResidential
Indicates that something is used or designated primarily for people to live in, rather than for commercial, industrial, or other non-living purposes.
-
E.
isResidentialBaseFor
Indicates that a location serves as the primary place of residence or home base for a person or group.
- 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_69d85a16c68c819099c1b547fbc87b32 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03ea4f13c819085d26fd32b5dca6f |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:20 a.m.