Triple
T13915121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Principal Sojourner |
E334601
|
entity |
| Predicate | rankWithinChapter |
P112272
|
FINISHED |
| Object | subordinate officer |
—
|
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: subordinate officer | Statement: [Principal Sojourner, rankWithinChapter, subordinate officer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankWithinChapter Context triple: [Principal Sojourner, rankWithinChapter, subordinate officer]
-
A.
roleInChapter
Indicates the specific function, position, or part an entity has within a particular chapter of a work.
-
B.
chapterNumber
Indicates the specific ordinal position a chapter occupies within a larger ordered work, such as a book or document.
-
C.
foundInChapter
Indicates that something (such as a concept, section, or element) is contained within or occurs in a specific chapter.
-
D.
basedOnChapter
Indicates that something (such as a work, section, or element) is derived from, adapted from, or primarily informed by a specific chapter.
-
E.
chapterOn
Indicates that one entity (typically a chapter) is about, discusses, or focuses on the subject represented by another 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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de27260ae08190be45b4b15898e365 |
completed | April 14, 2026, 11:38 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239524688190a0f2408c239cfcaa |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:16 p.m.