Triple
T13795480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Once Upon a Time in Shaolin |
E331502
|
entity |
| Predicate | listeningConditions |
P111487
|
FINISHED |
| Object | may be played at private listening events |
—
|
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: may be played at private listening events | Statement: [Once Upon a Time in Shaolin, listeningConditions, may be played at private listening events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: listeningConditions Context triple: [Once Upon a Time in Shaolin, listeningConditions, may be played at private listening events]
-
A.
listensOn
Indicates that a service or component is configured to receive and accept incoming communication on a specified network port or channel.
-
B.
mayHear
Indicates that one entity is permitted or able to hear sounds, speech, or audio produced by another entity.
-
C.
canHear
Indicates that one entity is able to perceive sounds produced by another entity.
-
D.
hearsFrom
Indicates that one entity receives information, communication, or a message from another entity.
-
E.
hears
Indicates that one entity perceives or detects sounds produced by another entity or source.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0259b0e4819081c11ced694384fb |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
| PDg | Predicate description generation | batch_69dcad0eea9881908f71e1eed9a2446b |
completed | April 13, 2026, 8:45 a.m. |
Created at: April 9, 2026, 10:11 p.m.