Triple
T1044922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Traitor |
E22555
|
entity |
| Predicate | dateOfWork |
P6878
|
FINISHED |
| Object | 1630s |
—
|
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: 1630s | Statement: [The Traitor, dateOfWork, 1630s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfWork Context triple: [The Traitor, dateOfWork, 1630s]
-
A.
workBy
Indicates that a work (such as a creation, product, or result) is produced, authored, or created by a particular agent or entity.
-
B.
workPeriod
Indicates the span of time during which an entity is engaged in a particular work or employment activity.
-
C.
dateOf
chosen
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
D.
hasWorkedFor
Indicates that an entity has been employed by or has provided work or services to another entity.
-
E.
workIncludes
Indicates that a work (such as a project, document, or creative piece) contains or incorporates another specified component, part, or element.
- 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_69a493d91478819094cc01fb65564bc1 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8f28c7c8190b9ca3749666bcbf3 |
completed | March 1, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69a4b72e3e488190b768005ad647886b |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.