Triple
T23837503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rindler wedge |
E590892
|
entity |
| Predicate | coordinateTime |
P133411
|
FINISHED |
| Object | Rindler time |
—
|
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: Rindler time | Statement: [Rindler wedge, coordinateTime, Rindler time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinateTime Context triple: [Rindler wedge, coordinateTime, Rindler time]
-
A.
timeCoordinate
chosen
Indicates a relationship where a specific time value is used to locate or reference an event, state, or object along a temporal axis or timeline.
-
B.
timeCoordinateType
Indicates the specific temporal reference system or framework used to define and interpret time coordinates for an event or entity.
-
C.
utcTime
Indicates that the associated time value is expressed in Coordinated Universal Time (UTC), independent of local time zones.
-
D.
timeCorrelation
Indicates that two events or states are related in time such that changes or occurrences in one are systematically associated with changes or occurrences in the other.
-
E.
timeSystem
Indicates a relationship where an entity uses, follows, or is defined within a particular system for measuring or organizing time.
- 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_69e25d1de32c8190a907afe9c3d6cd6d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c883c7108190b3cce6fec0b8609a |
completed | April 29, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 8:07 p.m.