Triple
T11200780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carthusian Order |
E265032
|
entity |
| Predicate | hasGeneralChapter |
P97830
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Carthusian Order, hasGeneralChapter, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeneralChapter Context triple: [Carthusian Order, hasGeneralChapter, yes]
-
A.
containsChapter
Indicates that one entity (typically a larger work or document) includes another entity as a chapter within its structure.
-
B.
hadChapterOf
Indicates that an entity (such as a book or document) includes or contains a specific chapter as one of its parts.
-
C.
hasLocalChaptersIn
Indicates that an organization maintains one or more local chapters or branches within a specified geographic area or location.
-
D.
containsSubchapter
Indicates that one chapter or section includes another, more specific subchapter as a part of its structure.
-
E.
hasWorkingChaptersReadPubliclyBy
Indicates that some or all working chapters of a work have been read aloud or presented in public by a specified entity.
- F. None of above. chosen
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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8c36c188190bfa4d5f8e6cbbbea |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69d77062271c8190b63da714ab5beff9 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:29 p.m.