Triple
T4606775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Blue Pool |
E100454
|
entity |
| Predicate | hasAmenityNearby |
P5648
|
FINISHED |
| Object | restrooms |
—
|
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: restrooms | Statement: [Big Blue Pool, hasAmenityNearby, restrooms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAmenityNearby Context triple: [Big Blue Pool, hasAmenityNearby, restrooms]
-
A.
hasNearbyFacility
chosen
Indicates that one entity is located close to or in the vicinity of a particular facility.
-
B.
hasAttractionNearby
Indicates that one entity is located close to another entity that serves as an attraction or point of interest.
-
C.
hasNearbyLandUse
Indicates that one land area is located close to another area characterized by a specific type of land use.
-
D.
nearbyVenue
Indicates that one venue is located close to another venue in physical space.
-
E.
meetsNear
Indicates that two entities meet or come together at a location that is in close proximity to a specified reference point or 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_69bd43cce1e08190a07d53af6a9b6c24 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd599c50d08190ab226cd0691e29f9 |
completed | March 20, 2026, 2:28 p.m. |
| PD | Predicate disambiguation | batch_69bd522e2d5c8190937d0b5574f78f99 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.