Triple
T32043801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milne universe model |
E818283
|
entity |
| Predicate | usesSpacetime |
P119641
|
FINISHED |
| Object | Minkowski spacetime |
—
|
NE NERFINISHED |
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: Minkowski spacetime | Statement: [Milne universe model, usesSpacetime, Minkowski spacetime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSpacetime Context triple: [Milne universe model, usesSpacetime, Minkowski spacetime]
-
A.
associatedSpacetime
chosen
Indicates a relationship where an entity is linked to, or situated within, a particular spacetime region or context.
-
B.
hasSpacetimeRegion
Indicates that something occupies, is associated with, or is bounded by a specific region in spacetime.
-
C.
usesTimeTravelFor
Indicates a relationship where an entity employs time travel as a means or method to achieve, affect, or interact with another entity or objective.
-
D.
usesSpace
Indicates that one entity occupies, consumes, or makes use of physical or conceptual space associated with another entity.
-
E.
usesSpacecraft
Indicates that one entity operates, employs, or relies on a spacecraft to perform an action or fulfill a function in relation to another entity or context.
- 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_69f348fcfb648190859f6be5e04b7cfe |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 1, 2026, 12:19 a.m.