Triple
T33829593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eta Aquariids |
E867058
|
entity |
| Predicate | typicalObservationCondition |
P56761
|
FINISHED |
| Object | dark, clear skies |
—
|
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: dark, clear skies | Statement: [Eta Aquariids, typicalObservationCondition, dark, clear skies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalObservationCondition Context triple: [Eta Aquariids, typicalObservationCondition, dark, clear skies]
-
A.
typicalWeatherFeature
Indicates a weather condition or pattern that commonly characterizes a place or time period.
-
B.
typicalTrackCondition
Indicates the usual or standard state or quality of a track under normal conditions.
-
C.
environmentalCondition
Indicates the state or characteristics of the surrounding physical environment that affect or describe a situation, process, or entity.
-
D.
hasObservationCondition
Indicates that an observation is associated with a specific condition or set of circumstances under which it was made.
-
E.
typicalCircumstance
chosen
Indicates the usual or commonly occurring situation, condition, or context in which an event, action, or relationship typically takes place.
- 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_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:46 a.m.