Triple
T10773086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Récoltes et Semailles |
E254129
|
entity |
| Predicate | endTimeOfWriting |
P81904
|
FINISHED |
| Object | around 1986 |
—
|
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: around 1986 | Statement: [Récoltes et Semailles, endTimeOfWriting, around 1986]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endTimeOfWriting Context triple: [Récoltes et Semailles, endTimeOfWriting, around 1986]
-
A.
endTimeAsCapital
Indicates that a specified time marks the ending point of an event, process, or state in the role of its designated capital or primary endpoint.
-
B.
compositionEndTime
chosen
Indicates the point in time at which a composition or creative work is considered to have been completed.
-
C.
writtenDuring
Indicates that the creation or authorship of something took place within a specified time period or historical event.
-
D.
hasDateWritten
Indicates that something is associated with the specific date on which it was written.
-
E.
timeOfSettingEnd
Indicates the point in time at which a specified setting, condition, or configuration ceases to be in effect.
- 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d7329b27748190bd0e2569c7972fd1 |
completed | April 9, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69d6f31455648190b5c24690487b1b54 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:16 p.m.