Triple
T21472501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fletcher–Munson equal-loudness contours |
E529765
|
entity |
| Predicate | graphAxis |
P41648
|
FINISHED |
| Object | frequency |
—
|
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: frequency | Statement: [Fletcher–Munson equal-loudness contours, graphAxis, frequency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: graphAxis Context triple: [Fletcher–Munson equal-loudness contours, graphAxis, frequency]
-
A.
visualAxis
Indicates a directional line of sight or viewing orientation from an observer or object toward a visual target.
-
B.
coordinateAxis
Indicates that one entity serves as a reference axis or directional basis for positioning, measuring, or orienting another entity in a coordinate system.
-
C.
yAxisRepresents
chosen
Indicates that the y-axis in a chart or graph corresponds to and measures a particular variable, quantity, or category.
-
D.
axesType
Indicates the type or configuration of axes associated with an entity, such as their orientation, scale, or dimensional setup.
-
E.
horizontalAxis
Indicates that one entity serves as the horizontal reference line or direction along which another entity is oriented, measured, or arranged.
- 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_69e0c459acb481909bb6ee452a0045c7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea14756081908c615590c68904d5 |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:19 p.m.