Triple
T30285866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purewell |
E770233
|
entity |
| Predicate | hasLocalAreaStatus |
P60379
|
FINISHED |
| Object | local 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: local area | Statement: [Purewell, hasLocalAreaStatus, local area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalAreaStatus Context triple: [Purewell, hasLocalAreaStatus, local area]
-
A.
localStatus
Indicates the current condition or state of an entity within a specific local context or environment.
-
B.
hasNeighbourhoodStatus
chosen
Indicates that an entity has a particular status, classification, or condition specifically in relation to a given neighbourhood.
-
C.
hasLocalSupport
Indicates that an entity receives backing, endorsement, or assistance from people or organizations within its immediate geographic or community area.
-
D.
locationStatus
Indicates the current state or condition of an entity with respect to a specific location (e.g., present, absent, en route, or unknown).
-
E.
hasNearbyGeographicalArea
Indicates that one geographical area is located in close spatial proximity to another geographical 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_69f224875c288190a9b96b975006ec4a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:46 p.m.