Triple
T1783790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cartesian coordinate system |
E39344
|
entity |
| Predicate | usesAxis |
P32356
|
FINISHED |
| Object | x-axis |
—
|
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-axis | Statement: [Cartesian coordinate system, usesAxis, x-axis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAxis Context triple: [Cartesian coordinate system, usesAxis, x-axis]
-
A.
isMajorAxisFor
Indicates that something serves as the primary or longest axis that defines the main directional or structural orientation of another object or system.
-
B.
usesIndicator
Indicates that one entity employs or relies on another entity as an indicator, signal, or metric for assessment, decision-making, or interpretation.
-
C.
axeType
Indicates the specific kind or category of axe associated with an entity or action.
-
D.
usesAttribute
Indicates that one entity employs, relies on, or makes use of a specific attribute of another entity in performing an action or defining a relationship.
-
E.
shaftOrientation
Indicates the directional alignment or angle at which a shaft is positioned or oriented relative to a reference frame or object.
- F. None of above. chosen
Provenance (4 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_69a88630519c8190a17addd83c4a3ef4 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab75457e54819096b8c6ae8c65550c |
completed | March 7, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69aa61d165688190924962a98e07ff69 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab75444d28819091c393e62fc97f82 |
completed | March 7, 2026, 12:45 a.m. |
Created at: March 4, 2026, 7:31 p.m.