Triple
T18443023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BK3N |
E450578
|
entity |
| Predicate | redshiftFrame |
P131617
|
FINISHED |
| Object | local flow |
—
|
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: local flow | Statement: [BK3N, redshiftFrame, local flow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redshiftFrame Context triple: [BK3N, redshiftFrame, local flow]
-
A.
redshift
Indicates that the observed wavelength of light or other electromagnetic radiation from an object is shifted toward longer (redder) wavelengths, typically due to relative motion away from the observer or cosmic expansion.
-
B.
redshift_z
Indicates the cosmological redshift value associated with an object or event, representing how much its emitted light has been stretched by the expansion of the universe.
-
C.
occursAtRedshift
Indicates that an event or phenomenon takes place at a specified cosmological redshift value.
-
D.
digitalZoom
Indicates that an image or video is magnified by digitally enlarging pixels rather than by using optical lens adjustment.
-
E.
frame
Indicates placing or presenting something within a particular context, structure, or perspective that shapes how it is interpreted.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51c12a0248190a848a1fe833a1975 |
completed | April 19, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2aa72c8190a40854a7a52081e2 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:30 a.m.