Triple
T19686293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Butterfly Cluster |
E472718
|
entity |
| Predicate | observingRequirement |
P104432
|
FINISHED |
| Object | dark skies recommended |
—
|
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 skies recommended | Statement: [Butterfly Cluster, observingRequirement, dark skies recommended]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observingRequirement Context triple: [Butterfly Cluster, observingRequirement, dark skies recommended]
-
A.
hasObservationRequirement
chosen
Indicates that one entity imposes or specifies an observation-related condition or requirement that must be satisfied by another entity or process.
-
B.
observationalVisibility
Indicates that one entity is able to observe or visually perceive another entity under given conditions.
-
C.
observanceRequires
Indicates that carrying out a particular observance or practice is contingent upon, or must be accompanied by, the fulfillment of a specified requirement or condition.
-
D.
observedBy
Indicates that an entity is perceived, monitored, or recorded by another entity acting as the observer.
-
E.
observedFor
Indicates that one entity is monitored, watched, or examined over a period of time for the benefit or analysis of 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6420c3f50819082b64b1fa4335e56 |
completed | April 20, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:45 p.m.