Triple
T8161568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poplars, Spring |
E190586
|
entity |
| Predicate | portraysTimeOfYear |
P59956
|
FINISHED |
| Object | spring |
—
|
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: spring | Statement: [Poplars, Spring, portraysTimeOfYear, spring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portraysTimeOfYear Context triple: [Poplars, Spring, portraysTimeOfYear, spring]
-
A.
timeOfYearPresented
chosen
Indicates the specific time or season of the year during which something is presented or takes place.
-
B.
seasonCharacterization
Indicates how a particular season is described, defined, or characterized in terms of its qualities or attributes.
-
C.
occursInSeasonInNorthernHemisphere
Indicates that an event or phenomenon takes place during a specified season as defined for the Northern Hemisphere.
-
D.
typicalSeasonTiming
Indicates the usual time period or season during which something normally occurs or is expected to take place.
-
E.
seasonCulminatesIn
Indicates that a particular season reaches its peak, conclusion, or defining outcome in the specified event or state.
- 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_69ca82c0ef14819083713f4473dd847c |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb455559188190bf95d9d93bb76002 |
completed | March 31, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69cb36a4c40c81909f60aef0e1624c13 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:38 p.m.