Triple
T29372213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YM-2151 |
E744882
|
entity |
| Predicate | hasPhaseModulation |
P23647
|
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: [YM-2151, hasPhaseModulation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhaseModulation Context triple: [YM-2151, hasPhaseModulation, yes]
-
A.
hasPhaseCoefficient
Indicates that one entity is associated with a numerical coefficient quantifying its phase-related behavior or contribution in a given process or system.
-
B.
usesModulation
chosen
Indicates that one entity applies or employs a particular modulation method or scheme in relation to another entity or process.
-
C.
modulationIndex
Indicates the degree to which one signal or factor varies or controls another signal’s amplitude, frequency, or phase in a modulation process.
-
D.
maximumPhase
Indicates that one entity represents the highest or final phase, stage, or level reached within a defined sequence or process involving another entity.
-
E.
definesModulation
Indicates that one entity specifies or determines how another entity is modulated or altered in its behavior, intensity, 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 28, 2026, 2:28 p.m.