Triple
T243698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newtonian absolute time |
E4989
|
entity |
| Predicate | flowsAt |
P9749
|
FINISHED |
| Object | constant rate |
—
|
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: constant rate | Statement: [Newtonian absolute time, flowsAt, constant rate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowsAt Context triple: [Newtonian absolute time, flowsAt, constant rate]
-
A.
flowsPast
Indicates that one entity (typically a fluid or river) moves in a continuous stream alongside and beyond another entity, passing by its location.
-
B.
outflow
Indicates the movement or discharge of something from an origin or source to the outside or to another location.
-
C.
drainsInto
Indicates that one entity serves as a source or conduit whose contents or flow are directed into another entity.
-
D.
flowControl
Indicates a relationship where one entity regulates, directs, or manages the rate or sequence of another entity’s operations or movement.
-
E.
downstreamFrom
Indicates that one entity is located or occurs at a point further along the natural flow or direction of another entity, typically in a linear or directional system such as a river, pipeline, or process sequence.
- 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.