Triple
T33829600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eta Aquariids |
E867058
|
entity |
| Predicate | typicalObserverAdvice |
P151327
|
FINISHED |
| Object | observe after radiant rises well above horizon |
—
|
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: observe after radiant rises well above horizon | Statement: [Eta Aquariids, typicalObserverAdvice, observe after radiant rises well above horizon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalObserverAdvice Context triple: [Eta Aquariids, typicalObserverAdvice, observe after radiant rises well above horizon]
-
A.
observerConcern
Indicates that an observer has a concern, worry, or critical attention directed toward another entity or situation.
-
B.
typicallyObserves
Indicates that one entity, in the normal or usual course of events, observes, watches, or monitors another entity.
-
C.
ignoredAdviceOf
Indicates that one entity did not follow or act upon the advice given by another entity.
-
D.
mayObserve
Indicates that one entity is permitted or allowed to observe, monitor, or watch another entity or process.
-
E.
advisedBehavior
chosen
Indicates that one entity recommends or counsels a particular behavior or course of action to another entity.
- 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.