Triple
T36791868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Letter to Maris the Persian |
E909074
|
entity |
| Predicate | includedInDossier |
P200859
|
FINISHED |
| Object | Three Chapters |
E63372
|
NE 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: Three Chapters | Statement: [Letter to Maris the Persian, includedInDossier, Three Chapters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedInDossier Context triple: [Letter to Maris the Persian, includedInDossier, Three Chapters]
-
A.
includedInDocument
chosen
Indicates that one entity is contained or referenced within a particular document.
-
B.
documentTypeIncluded
Indicates that a particular document type is contained within, or is part of, a specified set or collection of document types.
-
C.
containedInDocumentBy
Indicates that one entity is included or referenced within a document that is associated with or provided by another entity.
-
D.
includedBy
Indicates that one entity is contained within, encompassed by, or treated as a subset or member of another entity.
-
E.
worksForInclusionIn
Indicates that one entity performs work or contributes efforts toward being included in, or becoming part of, another entity (such as a group, project, or collection).
- F. None of above.
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_69f76e7a937c81909ed7359641e670f6 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3d17a7e32081909273c276a7a087c2 |
completed | June 25, 2026, 11:57 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.