Triple
T20684215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swimming |
E508371
|
entity |
| Predicate | canBePracticedIn |
P66256
|
FINISHED |
| Object | Swimming pool |
—
|
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: Swimming pool | Statement: [Swimming, canBePracticedIn, Swimming pool]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBePracticedIn Context triple: [Swimming, canBePracticedIn, Swimming pool]
-
A.
isPracticedBy
Indicates that an activity, skill, or discipline is regularly performed or carried out by a particular entity.
-
B.
isPracticedAt
chosen
Indicates that an activity, skill, or discipline is regularly performed or carried out at a particular location or context.
-
C.
practicedUnder
Indicates that one entity gained experience or training while working under the guidance, supervision, or mentorship of another entity.
-
D.
stillPracticedIn
Indicates that a tradition, custom, or practice continues to be actively carried out or observed in a specified place or context.
-
E.
sometimesPracticedAt
Indicates that an activity or practice occurs at a particular place or time on some occasions, but not regularly or consistently.
- 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_69e0b4c1ed408190b72dd26b1e33f8a1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6beaae5608190ac8cc64aa4717d53 |
completed | April 21, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69e5c03caee881908be4dd25796a03d5 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:45 a.m.