Triple
T15661764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minkowski metric η_{μν} |
E376582
|
entity |
| Predicate | coordinateNames |
P84195
|
FINISHED |
| Object | (t,x,y,z) |
—
|
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: (t,x,y,z) | Statement: [Minkowski metric η_{μν}, coordinateNames, (t,x,y,z)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinateNames
Context triple: [Minkowski metric η_{μν}, coordinateNames, (t,x,y,z)]
-
A.
coordinateSymbols
Indicates a relationship where one symbol is aligned or matched with another symbol in a coordinated or corresponding way.
-
B.
coordinateAxisName
chosen
Indicates the specific named axis (e.g., X, Y, Z or similar) along which a coordinate or measurement is defined in a coordinate system.
-
C.
coordinatesPositionsIn
Indicates that one entity organizes or aligns the positions or placement of other entities within a specified context or space.
-
D.
coordinateOrder
Indicates that one entity specifies the positional or sequential arrangement of coordinates for another entity.
-
E.
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.
- 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f0e2668819092e52712cddd0721 |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8b36a4819081cb5708fe77ef51 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:15 a.m.