Triple
T6410556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minkowski diagram |
E127693
|
entity |
| Predicate | spaceAxisOftenLabeled |
P67148
|
FINISHED |
| Object | x |
—
|
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: x | Statement: [Minkowski diagram, spaceAxisOftenLabeled, x]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spaceAxisOftenLabeled Context triple: [Minkowski diagram, spaceAxisOftenLabeled, x]
-
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.
transportAxis
Indicates a directional path or axis along which something is transported or moved from one location to another.
-
C.
formsAxisOf
Indicates that one entity serves together with another as the central line or primary axis around which a structure, system, or configuration is organized.
-
D.
usesAxis
Indicates that one entity employs or relies on another entity as a reference axis or basis for orientation, measurement, or organization.
-
E.
ridgeAxis
Indicates the central line or crest along the top of a ridge that defines its main axis or direction.
- 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_69c0083723d88190b1e37b19df162c08 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c068cf81508190bc09e58ec45bc858 |
completed | March 22, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69c060f40ecc8190b1df17b96767675c |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:41 p.m.