Triple
T2662161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cobbs Creek neighborhood |
E54748
|
entity |
| Predicate | hasPublicAmenity |
P37084
|
FINISHED |
| Object | public parks |
—
|
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: public parks | Statement: [Cobbs Creek neighborhood, hasPublicAmenity, public parks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicAmenity Context triple: [Cobbs Creek neighborhood, hasPublicAmenity, public parks]
-
A.
hasPublicSpaces
chosen
Indicates that an entity includes or provides areas that are accessible and usable by the general public.
-
B.
amenity
Indicates that one entity provides a useful facility, service, or feature that enhances the convenience or comfort of another entity.
-
C.
hasPublicSpaceAlong
Indicates that a public space (such as a park, plaza, or walkway) is located adjacent to or runs alongside the referenced feature or element.
-
D.
hasPublicHouse
Indicates that one entity possesses, operates, or is associated with a public house (such as a bar or pub) as part of its facilities or holdings.
-
E.
isPublicBuilding
Indicates that a building is designated for public use, access, or service rather than being privately owned or restricted.
- 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd969eff08190a206ad6424ba34d6 |
completed | March 7, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.