Triple
T23550309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Off He Goes |
E578019
|
entity |
| Predicate | isAcousticDriven |
P124206
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Off He Goes, isAcousticDriven, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAcousticDriven Context triple: [Off He Goes, isAcousticDriven, true]
-
A.
isAcoustic
chosen
Indicates that something produces sound using natural resonance or mechanical vibration rather than electronic amplification or synthesis.
-
B.
hasAcousticUse
Indicates that something is used or functions in relation to sound or acoustics.
-
C.
isPianoDriven
Indicates that something is primarily led, dominated, or characterized by the piano in its musical arrangement or performance.
-
D.
hasAcousticsSuitableFor
Indicates that something possesses acoustic properties that are appropriate or well-suited for a particular use, activity, or environment.
-
E.
isGuitarDriven
Indicates that something (such as a song, piece of music, or performance) is primarily led, dominated, or characterized by the sound and role of the guitar.
- 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_69e245fa93448190919cb04534560542 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1aece662081909022e7a29f966ca3 |
completed | April 29, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:11 p.m.