Triple
T35281336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memorymoog |
E1018940
|
entity |
| Predicate | hasPortamento |
P199685
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Memorymoog, hasPortamento, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPortamento Context triple: [Memorymoog, hasPortamento, yes]
-
A.
hasCadenza
Indicates that a musical work, passage, or performance includes or is associated with a cadenza section.
-
B.
hasOrnamentation
Indicates that an entity possesses decorative features or embellishments applied to its surface or structure.
-
C.
hasPitchBarrier
Indicates that there is a physical or structural barrier affecting or limiting the pitch (height or angle) between related entities.
-
D.
hasPortOn
Indicates that one entity possesses or is located adjacent to a port situated on another specified geographic or infrastructural feature (such as a coast, river, or lake).
-
E.
hasPitch
Indicates that one entity possesses or is characterized by a specific pitch (such as a tonal, acoustic, or frequency-related property).
- F. None of above. chosen
Provenance (4 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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff4fc6077c8190b8fd9b43fcfde986 |
completed | May 9, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69ff4e61fb648190a72f7918961ece9c |
completed | May 9, 2026, 3:10 p.m. |
| PDg | Predicate description generation | batch_69ff4fc5289c819084abd5ede185e96b |
completed | May 9, 2026, 3:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.