Triple
T32921809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inspired Version |
E842162
|
entity |
| Predicate | completedMainRevision |
P121866
|
FINISHED |
| Object | mid-1830s |
—
|
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: mid-1830s | Statement: [Inspired Version, completedMainRevision, mid-1830s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: completedMainRevision Context triple: [Inspired Version, completedMainRevision, mid-1830s]
-
A.
revisedVersionCompletion
Indicates that one entity represents the completed or finalized form of a revised version of another entity.
-
B.
completionDateMainLine
chosen
Indicates the date on which the primary or main phase of an activity, project, or process is completed.
-
C.
finalVersion
Indicates that an entity represents the completed, authoritative, and no-longer-changeable version of another entity or work.
-
D.
completedAfter
Indicates that one event or task was finished at a later time than another specified event or task.
-
E.
coreRevision
Indicates that one entity is a fundamental or primary revision of another, representing a central update or modification in a versioning or editing process.
- 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: May 1, 2026, 1:19 a.m.