Triple
T523616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Common Sense |
E10869
|
entity |
| Predicate | mediumOfPerformance |
P9966
|
FINISHED |
| Object | 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: vocals | Statement: [Common Sense, mediumOfPerformance, vocals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediumOfPerformance Context triple: [Common Sense, mediumOfPerformance, vocals]
-
A.
medium
Indicates that an entity serves as the means, channel, or intermediary through which an action, communication, or effect is carried out between other entities.
-
B.
mediumOfInstruction
Indicates that a particular language or medium is used as the primary means of instruction or teaching in an educational context.
-
C.
performedWith
chosen
Indicates that an action or activity is carried out using, accompanied by, or in conjunction with a specified entity or instrument.
-
D.
usedMedium
Indicates that an action or communication was carried out through a particular medium or channel.
-
E.
secondaryMedium
Indicates that an entity is associated with an additional, non-primary medium or channel through which it is expressed, delivered, or communicated.
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1b4f01881908b408357ff113308 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f018129c81909494450fcba71b59 |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.