Triple
T6291671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Milli |
E141031
|
entity |
| Predicate | hasProminentElement |
P30328
|
FINISHED |
| Object | looped vocal sample |
—
|
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: looped vocal sample | Statement: [A Milli, hasProminentElement, looped vocal sample]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProminentElement Context triple: [A Milli, hasProminentElement, looped vocal sample]
-
A.
hasProminentAspect
chosen
Indicates that an entity possesses a particularly notable, dominant, or emphasized aspect or feature.
-
B.
hasProminence
Indicates that one entity stands out in importance, visibility, or influence relative to others within a given context.
-
C.
hasMinimumProminence
Indicates that an entity meets or exceeds a specified threshold level of prominence or importance within a given context.
-
D.
hasProminenceParent
Indicates that one entity derives its prominence, importance, or highlighted status from another entity that serves as its parent in a prominence hierarchy.
-
E.
hasIconicElement
Indicates that something contains or features a distinctive, widely recognized element that symbolizes its identity or significance.
- 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_69c008cdf2ac8190bb640c94478fb4ed |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0641ea224819097b6962e6014c690 |
completed | March 22, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69c060df0d8881908215575862ef6831 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:27 p.m.