Triple
T37663634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oneknowing |
E937769
|
entity |
| Predicate | hasListeningExperience |
P199036
|
FINISHED |
| Object | immersive |
—
|
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: immersive | Statement: [Oneknowing, hasListeningExperience, immersive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasListeningExperience Context triple: [Oneknowing, hasListeningExperience, immersive]
-
A.
hadListeningEventAt
Indicates that a listening event involving an entity occurred at a specific time or place.
-
B.
auditionedFor
Indicates that one entity formally tried out or performed in order to be considered for a role, position, or opportunity associated with another entity.
-
C.
hasCheckInExperience
Indicates that an entity has undergone, participated in, or possesses a record of a check-in process or event.
-
D.
hasPastExperience
Indicates that an entity has previously engaged in or undergone the specified activity, role, or situation in the past.
-
E.
heardBy
Indicates that a sound, message, or communication produced by one entity is perceived or received auditorily by another entity.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff1ba8694481909ceb36f26ca85612 |
completed | May 9, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69ff1b27f0f08190a9e74308c5b3d1ba |
completed | May 9, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_69ff1ba7494481908678a7a0f93dbd03 |
completed | May 9, 2026, 11:33 a.m. |
Created at: May 3, 2026, 4:18 p.m.