Triple
T1463336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lorentz contraction |
E31562
|
entity |
| Predicate | contractedLengthMeasuredIn |
P24236
|
FINISHED |
| Object | frame where object is moving |
—
|
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: frame where object is moving | Statement: [Lorentz contraction, contractedLengthMeasuredIn, frame where object is moving]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contractedLengthMeasuredIn Context triple: [Lorentz contraction, contractedLengthMeasuredIn, frame where object is moving]
-
A.
approximateLengthInMeters
Indicates the estimated or roughly measured length of something expressed in meters.
-
B.
measuredBy
chosen
Indicates that something’s quantity, extent, or value is determined or expressed using a particular measurement method, instrument, or unit.
-
C.
length
Indicates a measurement relationship where a value specifies how long something is from one end to the other.
-
D.
measuredProperty
Indicates that the subject is a measurement that quantifies or assesses the specified property of an entity.
-
E.
typicalLength
Indicates the usual or characteristic length associated with an entity or phenomenon.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c5b89708819084fb9ba4ff293b8b |
completed | March 1, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69a4c48121e48190946c23c583e5fb64 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.