Triple
T34390151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaius Pius Esuvius Tetricus |
E882672
|
entity |
| Predicate | laterHeld |
P24273
|
FINISHED |
| Object | senatorial rank under Aurelian |
—
|
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: senatorial rank under Aurelian | Statement: [Gaius Pius Esuvius Tetricus, laterHeld, senatorial rank under Aurelian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterHeld Context triple: [Gaius Pius Esuvius Tetricus, laterHeld, senatorial rank under Aurelian]
-
A.
laterHeldBy
Indicates that an entity was possessed, controlled, or owned by another entity at a subsequent time after an earlier state or holder.
-
B.
heldAfter
chosen
Indicates that one event or state occurs or is maintained at some point in time after another specified event or state.
-
C.
heldFor
Indicates that something is kept in custody, possession, or reservation on behalf of someone or for a specified purpose or duration.
-
D.
heldOn
Indicates that an event or activity takes place at a specific time, date, or occasion.
-
E.
heldTo
Indicates that one entity is obligated, bound, or accountable to another entity, standard, or agreement.
- 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_69f349c0219881909393bbbc1edc8161 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a00262d71488190a769783fb09e5803 |
completed | May 10, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_6a0023985f148190a335a3fb93e9981e |
completed | May 10, 2026, 6:20 a.m. |
Created at: May 1, 2026, 1:59 a.m.