Triple
T32193460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sport Sharewood |
E822332
|
entity |
| Predicate | escapesVia |
P165484
|
FINISHED |
| Object | magical 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: magical swimming pool | Statement: [Sport Sharewood, escapesVia, magical swimming pool]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: escapesVia Context triple: [Sport Sharewood, escapesVia, magical swimming pool]
-
A.
escapesOn
chosen
Indicates that one entity flees, breaks free, or gets away by means of or via another entity (such as a route, method, or vehicle).
-
B.
escapesWith
Indicates that one entity flees or breaks free from a situation, place, or constraint together with another entity as a companion or accomplice.
-
C.
escapeManner
Indicates the manner or way in which an entity escapes from a situation, place, or constraint.
-
D.
escapeLocation
Indicates that an entity moves away from or leaves a location to avoid danger, capture, or an undesirable situation.
-
E.
escapeMechanism
Indicates a means or method by which an entity avoids, evades, or breaks free from a threat, constraint, or controlling influence.
- 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_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bb35369c8190992fe7dad36a2a9d |
completed | May 3, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:35 a.m.