Triple
T4178172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doctrine of Essence |
E86527
|
entity |
| Predicate | workDate |
P7950
|
FINISHED |
| Object | 1812–1816 |
—
|
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: 1812–1816 | Statement: [Doctrine of Essence, workDate, 1812–1816]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workDate Context triple: [Doctrine of Essence, workDate, 1812–1816]
-
A.
workPeriod
chosen
Indicates the span of time during which an entity is engaged in a particular work or employment activity.
-
B.
worksOver
Indicates that one entity performs work that extends beyond or exceeds a certain limit, threshold, or standard associated with another entity.
-
C.
commutationDate
Indicates the date on which a sentence or penalty is formally reduced, altered, or commuted.
-
D.
workChronicles
Indicates that one entity documents, records, or narrates the work-related activities, history, or experiences of another entity.
-
E.
workBy
Indicates that a work (such as a creation, product, or result) is produced, authored, or created by a particular agent or entity.
- 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_69aed93de98c8190ad838ce507b77c8a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af07078cb081909f64326b12522410 |
completed | March 9, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69af019155448190b19868583272513f |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:45 p.m.