Triple
T244279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lorentz transformation |
E5001
|
entity |
| Predicate | actsOn |
P9769
|
FINISHED |
| Object | spacetime 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: spacetime four-vectors | Statement: [Lorentz transformation, actsOn, spacetime four-vectors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actsOn Context triple: [Lorentz transformation, actsOn, spacetime four-vectors]
-
A.
actsOnBehalfOf
Indicates that one entity performs actions or makes decisions as a representative or proxy for another entity.
-
B.
endsOn
Indicates that one entity terminates or concludes precisely at the boundary or endpoint of another entity.
-
C.
createdByAct
Indicates that something came into existence or was produced as the result of a specific act or action.
-
D.
appointedFor
Indicates that an entity has been officially assigned or designated to perform a specific role, task, or function for another entity or purpose.
-
E.
enactedBy
Indicates that a law, policy, or formal measure is officially established or brought into effect by a specific authority or governing body.
- 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_69a257c3d0708190b0871c4269d273e6 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25dcd2b208190855d5d8d70a3acfc |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b62839c8190824064fe5da6a92a |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25dcba5148190ab80fd14c7cf4bb4 |
completed | Feb. 28, 2026, 3:15 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.