Triple
T6903300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | magister officiorum |
E159544
|
entity |
| Predicate | positionEstablishedInPeriod |
P28028
|
FINISHED |
| Object | late 3rd century |
—
|
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: late 3rd century | Statement: [magister officiorum, positionEstablishedInPeriod, late 3rd century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionEstablishedInPeriod Context triple: [magister officiorum, positionEstablishedInPeriod, late 3rd century]
-
A.
positionEstablishedIn
chosen
Indicates the point in time or event when a particular position, role, or office was formally created or instituted.
-
B.
positionEstablishedFor
Indicates that a specific role or job position has been formally created or set up for a particular entity or purpose.
-
C.
locationPeriod
Indicates that an entity is associated with being at a particular location during a specified time period.
-
D.
positionStartTime
Indicates the time at which a position, role, or placement begins.
-
E.
positionHeld
Indicates that an entity occupies or has occupied a specific role, job, office, or position within an organization or context.
- 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_69c6883822e0819091e321526f20ae0a |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d988a5b48190a9238047e86f314c |
completed | March 27, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b7681481909ec50509b19fcf81 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:25 p.m.