Triple
T1372550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Right and Left |
E30144
|
entity |
| Predicate | timeOfDayDepicted |
P2325
|
FINISHED |
| Object | overcast daylight |
—
|
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: overcast daylight | Statement: [Right and Left, timeOfDayDepicted, overcast daylight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfDayDepicted Context triple: [Right and Left, timeOfDayDepicted, overcast daylight]
-
A.
hasTimeOfDay
Indicates that a situation, event, or state occurs during, or is associated with, a specific part of the day (e.g., morning, afternoon, evening, night).
-
B.
budTime
Indicates the time or period when a bud forms or begins to develop.
-
C.
dayLengthCharacteristic
Indicates a relationship where an entity is characterized or defined by the length or duration of its day.
-
D.
timeDescribedAs
chosen
Indicates that a specific time or temporal interval is characterized, labeled, or expressed using a particular description or representation.
-
E.
timeType
Indicates the specific temporal category or classification associated with a time-related entity or value (e.g., duration, point in time, interval, or recurrence type).
- 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_69a498f912008190a376a98b207b2071 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c2f4889881908103473a0173e23f |
completed | March 1, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69a4befb08b88190be966fa1aadd4bcd |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:57 p.m.