Triple
T378918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minkowski space-time |
E8632
|
entity |
| Predicate | invariantQuantity |
P9160
|
FINISHED |
| Object | space-time interval |
—
|
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: space-time interval | Statement: [Minkowski space-time, invariantQuantity, space-time interval]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: invariantQuantity Context triple: [Minkowski space-time, invariantQuantity, space-time interval]
-
A.
quantityType
Indicates that one entity is the type or category of quantity to which another entity (a specific measured or measurable amount) belongs.
-
B.
invariantType
chosen
Indicates that one entity has a type or classification that remains constant or unchanged under specified conditions or transformations.
-
C.
isLocalQuantity
Indicates that a quantity is specific to a particular context, location, or subsystem rather than being globally applicable.
-
D.
isQuantumOf
Indicates that one entity represents a discrete, indivisible unit or packet of the other entity in a quantized relationship.
-
E.
quantifies
Indicates that one entity expresses or specifies the amount, number, or degree of another entity.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec2974988190a1d6316cbb5159c8 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e964d4b481909290e474b0341e3c |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.