Triple
T29395683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nohkalikai Falls |
E745492
|
entity |
| Predicate | hasPlungePool |
P181328
|
FINISHED |
| Object | deep natural pool at base |
—
|
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: deep natural pool at base | Statement: [Nohkalikai Falls, hasPlungePool, deep natural pool at base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlungePool Context triple: [Nohkalikai Falls, hasPlungePool, deep natural pool at base]
-
A.
hasSwimmingPool
Indicates that the subject possesses or includes a swimming pool as one of its features.
-
B.
hasSwimmingAreaType
Indicates that an entity’s swimming area is classified as a specific type or category (e.g., indoor pool, open water, designated beach zone).
-
C.
hasDivingBoards
Indicates that one entity possesses or is equipped with one or more diving boards.
-
D.
hasJacuzzi
Indicates that one entity possesses, includes, or is equipped with a jacuzzi.
-
E.
homePool
Indicates that an entity is associated with or belongs to a primary or default pool, typically used as its main or originating pool.
- F. None of above. chosen
Provenance (4 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
| PDg | Predicate description generation | batch_69f7688cea58819098bdfd7c80df7634 |
completed | May 3, 2026, 3:23 p.m. |
Created at: April 28, 2026, 2:46 p.m.