Triple
T15661761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minkowski metric η_{μν} |
E376582
|
entity |
| Predicate | componentsInStandardCoordinates |
P105386
|
FINISHED |
| Object | diag(-1,1,1,1) |
—
|
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: diag(-1,1,1,1) | Statement: [Minkowski metric η_{μν}, componentsInStandardCoordinates, diag(-1,1,1,1)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentsInStandardCoordinates
Context triple: [Minkowski metric η_{μν}, componentsInStandardCoordinates, diag(-1,1,1,1)]
-
A.
coordinateComponent
Indicates that one entity is a component or part of a larger coordinated structure or system involving the other entity.
-
B.
dimensionOfComponents
Indicates that a specified dimension value is associated with, or applies to, the components of an object or system.
-
C.
usesCoordinateRepresentation
chosen
Indicates that one entity expresses or handles another entity in terms of a specific coordinate-based representation.
-
D.
coordinateSystem
Indicates that one entity defines or uses a particular spatial or reference coordinate system in relation to another entity.
-
E.
componentPosition
Indicates the spatial or logical placement of a component relative to a larger structure or system.
- 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.