Triple
T18772471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messier 11 |
E459048
|
entity |
| Predicate | hasObservationSeason |
P1014
|
FINISHED |
| Object | northern summer |
—
|
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: northern summer | Statement: [Messier 11, hasObservationSeason, northern summer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasObservationSeason Context triple: [Messier 11, hasObservationSeason, northern summer]
-
A.
hasObservation
Indicates that an entity records, contains, or is associated with a specific observation or measured instance.
-
B.
hasFieldSeason
Indicates that an entity is associated with a specific field season during which related activities, observations, or operations take place.
-
C.
hasSeason
chosen
Indicates that an entity possesses, occurs during, or is associated with a particular season or set of seasons.
-
D.
hasSeasonScope
Indicates that something is applicable, valid, or relevant only within a specified season or seasonal period.
-
E.
hasSeasonalSpecies
Indicates that certain species are present or occur only during specific seasons in relation to a given context or location.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e59336a6b08190819595a55177264e |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.