Triple
T35281379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sub Phatty |
E1018941
|
entity |
| Predicate | hasModulationDestination |
P119850
|
FINISHED |
| Object | pitch |
—
|
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: pitch | Statement: [Sub Phatty, hasModulationDestination, pitch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModulationDestination Context triple: [Sub Phatty, hasModulationDestination, pitch]
-
A.
usesModulation
Indicates that one entity applies or employs a particular modulation method or scheme in relation to another entity or process.
-
B.
definesModulation
chosen
Indicates that one entity specifies or determines how another entity is modulated or altered in its behavior, intensity, or effect.
-
C.
hasDetuneFunction
Indicates that an entity possesses a function or capability to adjust or alter tuning from a standard reference.
-
D.
receivesModulatoryInputFrom
Indicates that one entity’s activity is influenced or regulated by signals originating from another entity.
-
E.
hasAmplifier
Indicates that one entity functions as an amplifier for another entity, enhancing or boosting its signal, power, or effect.
- 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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff0b6bc4a88190bf1d38c6ea26bcdc |
completed | May 9, 2026, 10:24 a.m. |
| PD | Predicate disambiguation | batch_69ff082a22f4819095ded971dbd8ea7b |
completed | May 9, 2026, 10:10 a.m. |
Created at: May 3, 2026, 4:03 p.m.