Triple
T15661786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minkowski metric η_{μν} |
E376582
|
entity |
| Predicate | lowersIndicesOf |
P119647
|
FINISHED |
| Object | four-vectors |
—
|
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: four-vectors | Statement: [Minkowski metric η_{μν}, lowersIndicesOf, four-vectors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowersIndicesOf
Context triple: [Minkowski metric η_{μν}, lowersIndicesOf, four-vectors]
-
A.
lowerValueIndicates
Indicates that a smaller numerical value of a property or measurement corresponds to a greater degree, better outcome, or stronger presence of the relevant characteristic.
-
B.
loweredWhen
Indicates that one entity decreases or is reduced in value, level, or intensity when a specified condition involving another entity holds.
-
C.
hasLower
Indicates that one entity is positioned at a lower level, rank, or value relative to another entity.
-
D.
lowerRank
Indicates that one entity holds an inferior or subordinate rank, status, or position relative to another entity.
-
E.
lowerRankedOrder
Indicates that one entity holds a lower rank or priority in an ordered sequence relative to another entity.
- 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_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. |
| PDg | Predicate description generation | batch_69dff7f3016c8190ac68d76e65e07af4 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:15 a.m.