Triple
T23742798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hovercraft |
E586723
|
entity |
| Predicate | usesVocals |
P25705
|
FINISHED |
| Object | rarely uses conventional vocals |
—
|
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: rarely uses conventional vocals | Statement: [Hovercraft, usesVocals, rarely uses conventional vocals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesVocals Context triple: [Hovercraft, usesVocals, rarely uses conventional vocals]
-
A.
hasVocals
chosen
Indicates that the subject includes or features vocal elements, such as singing or spoken voice, rather than being purely instrumental or non-vocal.
-
B.
usesVocalSamples
Indicates that one entity incorporates recorded vocal sounds from another source into its own audio or musical production.
-
C.
usesVocalInstrument
Indicates that an entity performs or produces sound using their voice as a musical instrument.
-
D.
hasBackwardVocals
Indicates that the subject uses or contains backward (reversed) vocal audio in relation to the object.
-
E.
vocal
Indicates that an entity produces or is characterized by audible sounds, speech, or vocalizations.
- 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_69e24908efb08190bf755c3a9b91f222 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bad734b08190a4b3365df97c73e1 |
completed | April 29, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:11 p.m.