Triple
T7723710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nyquist plot |
E175076
|
entity |
| Predicate | axisType |
P67148
|
FINISHED |
| Object | real-imaginary plane |
—
|
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: real-imaginary plane | Statement: [Nyquist plot, axisType, real-imaginary plane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: axisType Context triple: [Nyquist plot, axisType, real-imaginary plane]
-
A.
coordinateAxis
chosen
Indicates that one entity serves as a reference axis or directional basis for positioning, measuring, or orienting another entity in a coordinate system.
-
B.
horizontalAxis
Indicates that one entity serves as the horizontal reference line or direction along which another entity is oriented, measured, or arranged.
-
C.
axisObjective
Indicates that an entity serves as a primary goal, target, or focal objective along a defined axis or strategic direction in a given context.
-
D.
transportAxis
Indicates a directional path or axis along which something is transported or moved from one location to another.
-
E.
yAxisRepresents
Indicates that the y-axis in a chart or graph corresponds to and measures a particular variable, quantity, or category.
- 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_69c6995d541c81909eaa646b1a8369a9 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7074eca4c8190bd51fd1b450729e8 |
completed | March 27, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69c7016a6cf88190b53bf4b958f0f302 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:05 p.m.