Triple
T24806413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lorenz attractor |
E620668
|
entity |
| Predicate | coordinateVariables |
P157325
|
FINISHED |
| Object | y |
—
|
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: y | Statement: [Lorenz attractor, coordinateVariables, y]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinateVariables Context triple: [Lorenz attractor, coordinateVariables, y]
-
A.
coordinateVariables
chosen
Indicates that the variables are aligned or paired together in a shared coordinate system or structured correspondence.
-
B.
coordinates
Indicates that one entity organizes, directs, or harmonizes the actions or efforts of another entity or group to achieve a unified outcome.
-
C.
coordinateTerm
Indicates that two terms are coordinate concepts at the same hierarchical level, typically sharing a common broader category without one being subordinate to the other.
-
D.
coordinateSymbols
Indicates a relationship where one symbol is aligned or matched with another symbol in a coordinated or corresponding way.
-
E.
coordinatesFunction
Indicates a relationship where one entity organizes, schedules, or manages the execution of a function or activity involving other entities.
- 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 4:50 a.m.