Triple
T23049124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greeting to the Sun |
E573958
|
entity |
| Predicate | poweredDuring |
P14386
|
FINISHED |
| Object | nighttime |
—
|
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: nighttime | Statement: [Greeting to the Sun, poweredDuring, nighttime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: poweredDuring Context triple: [Greeting to the Sun, poweredDuring, nighttime]
-
A.
inPowerDuring
Indicates that an entity holds a position of authority or governance throughout a specified time period.
-
B.
engagedWithPower
Indicates a relationship where an entity actively interacts, collaborates, or aligns with a source of authority, influence, or control.
-
C.
usesPowerFor
Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
-
D.
inPowerSince
Indicates the point in time from which an entity has continuously held a position of authority or power.
-
E.
powerBy
chosen
Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by 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_69e245b9c11481909d06c872214d21af |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1867b800881909fabf9dca994c9e7 |
completed | April 29, 2026, 4:18 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
Created at: April 17, 2026, 3:54 p.m.