Triple
T4565146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ko’okiri Body Plunge |
E121889
|
entity |
| Predicate | hasQueueEnvironment |
P13810
|
FINISHED |
| Object | outdoor |
—
|
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: outdoor | Statement: [Ko’okiri Body Plunge, hasQueueEnvironment, outdoor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQueueEnvironment Context triple: [Ko’okiri Body Plunge, hasQueueEnvironment, outdoor]
-
A.
hasQueue
Indicates that an entity maintains or is associated with a queue, typically representing an ordered list of items or tasks awaiting processing.
-
B.
hasQueueType
Indicates that an entity is associated with a specific type or category of queue.
-
C.
hasEnvironmentType
chosen
Indicates that an entity is associated with or occurs within a specific type or category of environment.
-
D.
hasWaitingArea
Indicates that an entity provides or includes a designated space where people can wait before receiving a service or proceeding to another area.
-
E.
hasEnvironmentalFunction
Indicates that an entity serves a specific role or purpose related to the environment, such as contributing to ecological processes, protection, or sustainability.
- 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_69bd463f156881908a99aca69c5721ac |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd589cde9081909b84186d700fc463 |
completed | March 20, 2026, 2:24 p.m. |
| PD | Predicate disambiguation | batch_69bd52254c648190a5144cfe8fa7e409 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.