Triple
T8023120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Without You |
E186785
|
entity |
| Predicate | containsInstrument |
P72278
|
FINISHED |
| Object | piano |
—
|
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: piano | Statement: [Without You, containsInstrument, piano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsInstrument Context triple: [Without You, containsInstrument, piano]
-
A.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
B.
includesInstruments
chosen
Indicates that one entity contains, involves, or makes use of one or more instruments as part of its composition or execution.
-
C.
containsInstrumentWithStatus
Indicates that an entity includes or is associated with an instrument that has a specified status.
-
D.
alsoAppliesInstrument
Indicates that a condition, rule, or characteristic that applies to one instrument also applies to another instrument.
-
E.
coInstrumentWith
Indicates that two or more entities are used together as instruments or means to perform the same action or achieve the same outcome.
- 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_69ca82ad4e2c8190a693e3c9e30fe66f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3e8fb6788190a16413051ec26988 |
completed | March 31, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69cb049253d08190bafcecfde493ab8b |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:21 p.m.