Triple
T21591331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sadeh |
E532785
|
entity |
| Predicate | timeInYear |
P31250
|
FINISHED |
| Object | 100 days before Nowruz |
—
|
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: 100 days before Nowruz | Statement: [Sadeh, timeInYear, 100 days before Nowruz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInYear Context triple: [Sadeh, timeInYear, 100 days before Nowruz]
-
A.
approximateTimeInYear
Indicates that one time-related entity represents an estimated or non-exact point or interval within a given year for another entity.
-
B.
yearPassed
Indicates that a specified number of calendar years has elapsed between two time points or events.
-
C.
timeOfYearPlayed
chosen
Indicates the specific time or season of the year during which an event or activity is performed or takes place.
-
D.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
E.
durationInYears
Indicates the length of time associated with something, measured in whole or fractional years.
- 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_69e0c46251648190876f0427cf2d321b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eefaddc8508190950b31e2df865ad1 |
completed | April 27, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69e632109d048190b4ac3f14fe48d1a0 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:32 p.m.