Triple
T20612920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messier 41 |
E506490
|
entity |
| Predicate | bestObservationMonth |
P36410
|
FINISHED |
| Object | February |
—
|
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: February | Statement: [Messier 41, bestObservationMonth, February]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestObservationMonth Context triple: [Messier 41, bestObservationMonth, February]
-
A.
bestVisibleMonthNorthernHemisphere
chosen
Indicates the month in which something is most optimally visible from locations in the Northern Hemisphere.
-
B.
bestHikingMonths
Indicates the months of the year during which hiking conditions are considered most favorable for a given place or trail.
-
C.
peakSeasonMonth
Indicates the month or months during which something (such as demand, activity, or occurrence) reaches its highest or most intense level.
-
D.
monthObserved
Indicates the month during which an event, observation, or measurement took place.
-
E.
bestObservedWith
Indicates that one entity is most effectively or appropriately observed, detected, or measured when used or considered together with another specified 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aad94dac8190921c7769a649c724 |
completed | April 20, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:41 a.m.