Triple
T4648465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 1432 |
E102230
|
entity |
| Predicate | bestObservedIn |
P34153
|
FINISHED |
| Object | autumn |
—
|
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: autumn | Statement: [NGC 1432, bestObservedIn, autumn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestObservedIn Context triple: [NGC 1432, bestObservedIn, autumn]
-
A.
bestObservedWith
Indicates that one entity is most effectively or appropriately observed, detected, or measured when used or considered together with another specified entity.
-
B.
isObservedIn
chosen
Indicates that something (such as a phenomenon, property, or behavior) is detected, recorded, or found to occur within a particular context, setting, or environment.
-
C.
observedBy
Indicates that an entity is perceived, monitored, or recorded by another entity acting as the observer.
-
D.
observedFor
Indicates that one entity is monitored, watched, or examined over a period of time for the benefit or analysis of another entity.
-
E.
dstObserved
Indicates that an entity has been observed, detected, or recorded as the destination of another entity or action.
- 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_69bd43d71a308190afea7280841b0de8 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd6632708c8190b627d99363ab062c |
completed | March 20, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69bd620fc5e081908325ac8e6a6384ab |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:14 p.m.