Triple
T28533722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EPIC |
E722105
|
entity |
| Predicate | enablesObservation |
P71680
|
FINISHED |
| Object | global diurnal cycle of the sunlit Earth |
—
|
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: global diurnal cycle of the sunlit Earth | Statement: [EPIC, enablesObservation, global diurnal cycle of the sunlit Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enablesObservation Context triple: [EPIC, enablesObservation, global diurnal cycle of the sunlit Earth]
-
A.
supportsObservation
chosen
Indicates that one entity provides evidence, context, or infrastructure that enables or strengthens the validity of an observation made about another entity.
-
B.
mayObserve
Indicates that one entity is permitted or allowed to observe, monitor, or watch another entity or process.
-
C.
observedFor
Indicates that one entity is monitored, watched, or examined over a period of time for the benefit or analysis of another entity.
-
D.
isObservedUsing
Indicates that an entity is observed or monitored by means of a specified instrument, method, or medium.
-
E.
observedBy
Indicates that an entity is perceived, monitored, or recorded by another entity acting as the observer.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 3:30 a.m.