Triple
T35585864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pymmes Park Lake |
E1028353
|
entity |
| Predicate | isAmenityFor |
P111097
|
FINISHED |
| Object | local community |
—
|
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 community | Statement: [Pymmes Park Lake, isAmenityFor, local community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAmenityFor Context triple: [Pymmes Park Lake, isAmenityFor, local community]
-
A.
hasCivicAmenity
Indicates that an entity possesses, provides, or is associated with a public facility or service intended for community use.
-
B.
amenity
Indicates that one entity provides a useful facility, service, or feature that enhances the convenience or comfort of another entity.
-
C.
amenityScope
Indicates the range or extent of services, facilities, or conveniences that an amenity provides or applies to.
-
D.
amenityContext
Indicates the situational or environmental setting in which an amenity is provided, used, or relevant.
-
E.
amenityFocus
chosen
Indicates a relationship where an amenity is specifically oriented toward, designed for, or primarily serving a particular focus or target (such as a user group, activity, or purpose).
- 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_69f76e0495a081909beced418558c0b4 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:04 p.m.