Triple
T33829569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eta Aquariids |
E867058
|
entity |
| Predicate | visibilityBestTime |
P150574
|
FINISHED |
| Object | pre-dawn |
—
|
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: pre-dawn | Statement: [Eta Aquariids, visibilityBestTime, pre-dawn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visibilityBestTime Context triple: [Eta Aquariids, visibilityBestTime, pre-dawn]
-
A.
observationBestTime
chosen
Indicates that there is an identified optimal or most suitable time period during which the observation of something should be made.
-
B.
bestTimeOfDayToVisit
Indicates the time of day during which visiting something is considered most optimal or desirable.
-
C.
isVisibleBestIn
Indicates that an entity is considered the most visible or prominent within a specified context or set.
-
D.
peakVisibility
Indicates the degree to which a peak (such as a mountain or summit) is visible from a given location or under certain conditions.
-
E.
bestTimeForPhotography
Indicates the most suitable or optimal time period for taking photographs, typically based on lighting or environmental conditions.
- 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:46 a.m.