Triple
T12098134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A New English Dictionary on Historical Principles |
E288121
|
entity |
| Predicate | projectStartApproximate |
P48368
|
FINISHED |
| Object | 1879 |
—
|
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: 1879 | Statement: [A New English Dictionary on Historical Principles, projectStartApproximate, 1879]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectStartApproximate Context triple: [A New English Dictionary on Historical Principles, projectStartApproximate, 1879]
-
A.
estimatedStartDate
Indicates the date on which something is expected or planned to begin, based on current information or projections.
-
B.
timeStartApprox
chosen
Indicates that the associated event or state begins at an approximate, rather than exact, point in time.
-
C.
projectLength
Indicates the duration or total time span over which a project is planned or executed.
-
D.
majorProjectStartPeriod
Indicates the time period during which a major project is initiated or begins.
-
E.
planningStarted
Indicates that the process of planning for a particular task, project, or event has been initiated.
- 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_69d6ab4964708190850585628b287b0c |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9178ad99c8190a54777b9bbe998bc |
completed | April 10, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69d915000454819089fee00022055599 |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:48 p.m.