Triple
T30874288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martinian |
E786431
|
entity |
| Predicate | officeBeforeElevation |
P193111
|
FINISHED |
| Object | magister officiorum |
—
|
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: magister officiorum | Statement: [Martinian, officeBeforeElevation, magister officiorum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeBeforeElevation Context triple: [Martinian, officeBeforeElevation, magister officiorum]
-
A.
officeBefore
chosen
Indicates that one office, position, or term is held or occurs earlier in time than another office, position, or term.
-
B.
elevatedTo
Indicates that one entity is promoted or raised to a higher rank, status, position, or level relative to another.
-
C.
officeHoldsSuccession
Indicates that one office or position is designated to succeed or follow another in an official line of succession.
-
D.
officeTransformedInto
Indicates that one office has been converted or changed into another office or a different type of space.
-
E.
office held level
Indicates the hierarchical level or rank at which an office or position is held within an organizational or governmental structure.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe9dfaa2d08190b2084f63f842eb6b |
completed | May 9, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69fe9bba947c81908b0b2b92a4d19b37 |
completed | May 9, 2026, 2:28 a.m. |
Created at: April 29, 2026, 8:48 p.m.