Triple
T2863181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fourteen anathemas against the Three Chapters |
E63373
|
entity |
| Predicate | documentStructure |
P22618
|
FINISHED |
| Object | series of numbered anathemas |
—
|
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: series of numbered anathemas | Statement: [Fourteen anathemas against the Three Chapters, documentStructure, series of numbered anathemas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentStructure Context triple: [Fourteen anathemas against the Three Chapters, documentStructure, series of numbered anathemas]
-
A.
textualStructure
chosen
Indicates how parts of a text are organized and related to each other within its overall structure.
-
B.
documentModel
Indicates that an entity serves as or is associated with a specific structured representation or schema of a document.
-
C.
doctypeSyntax
Indicates that one entity specifies or conforms to the syntax rules of a document type declaration (DOCTYPE) used in markup languages.
-
D.
documentationType
Indicates the specific category or kind of documentation associated with or required for an entity or process.
-
E.
documentForm
Indicates the specific format or structural type in which a document is presented or recorded.
- 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_69ab4c41e8c08190a9e8f5249cc12610 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdfb6e6988190b832ee05d8420633 |
completed | March 7, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69abdd123ec48190af50a1859aea50b7 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.