Triple
T15661789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minkowski metric η_{μν} |
E376582
|
entity |
| Predicate | lineElementForm |
P119648
|
FINISHED |
| Object | ds^2 = -c^2 dt^2 + dx^2 + dy^2 + dz^2 |
—
|
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: ds^2 = -c^2 dt^2 + dx^2 + dy^2 + dz^2 | Statement: [Minkowski metric η_{μν}, lineElementForm, ds^2 = -c^2 dt^2 + dx^2 + dy^2 + dz^2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineElementForm
Context triple: [Minkowski metric η_{μν}, lineElementForm, ds^2 = -c^2 dt^2 + dx^2 + dy^2 + dz^2]
-
A.
lineElement
Indicates a relationship where something functions as, or is identified as, an element or segment of a line within a larger linear structure or representation.
-
B.
formedLine
Indicates that an entity has arranged itself or others into a line or linear formation.
-
C.
lineUse
Indicates how a particular line (such as a route, track, or service line) is utilized or purposed within a system or network.
-
D.
lineType
Indicates the specific category or style of a line used in a representation, such as its function or visual convention.
-
E.
lineSymbol
Indicates that one entity is used as a line-style or line-representation symbol for 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.