Triple
T10454844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Far Ultraviolet Camera/Spectrograph |
E246523
|
entity |
| Predicate | dataRecordedOn |
P65789
|
FINISHED |
| Object | photographic film |
—
|
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: photographic film | Statement: [Far Ultraviolet Camera/Spectrograph, dataRecordedOn, photographic film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataRecordedOn Context triple: [Far Ultraviolet Camera/Spectrograph, dataRecordedOn, photographic film]
-
A.
recordedOnDate
Indicates the specific calendar date on which an event, action, or piece of information was formally recorded.
-
B.
timeRecorded
Indicates that a specific point or period in time has been captured and stored as associated with an event, action, or state.
-
C.
dataCollectedOn
chosen
Indicates that certain data was gathered, recorded, or measured at a specific point in time or on a particular date.
-
D.
firstRecordingDate
Indicates the date on which an entity’s first recording (e.g., audio, video, or similar captured performance) was made.
-
E.
capturedAt
Indicates the specific time or moment at which an entity was captured, recorded, or taken.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe47fee48190b38ec0466ff0165a |
completed | April 7, 2026, 12:53 p.m. |
| PD | Predicate disambiguation | batch_69d4fb7d353c8190a73f439a956c7606 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:17 p.m.