Triple
T288861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walden; or, Life in the Woods |
E5944
|
entity |
| Predicate | endOfExperiment |
P9293
|
FINISHED |
| Object | 1847 |
—
|
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: 1847 | Statement: [Walden; or, Life in the Woods, endOfExperiment, 1847]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfExperiment Context triple: [Walden; or, Life in the Woods, endOfExperiment, 1847]
-
A.
endEvent
Indicates that one event or process marks the termination or conclusion of another event or process.
-
B.
finalStep
Indicates that an action or state represents the last step or concluding stage in a process or sequence.
-
C.
officeEnded
Indicates that a person’s term in an office or position has concluded at a specified time or under certain conditions.
-
D.
concludedAt
Indicates the point in time at which an event, process, or relationship comes to an end or is completed.
-
E.
concludedBy
Indicates that an event, process, or state is brought to an end or finalized by a specific agent or entity.
- F. None of above. chosen
Provenance (4 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a25e2f5c0081908e548b314f5e986d |
completed | Feb. 28, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69a25b7c1448819082064f474633acd5 |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25d3463648190ac716d7475378536 |
completed | Feb. 28, 2026, 3:12 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.