Triple
T4558903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman magistracy |
E120545
|
entity |
| Predicate | continuedInModifiedFormDuring |
P42870
|
FINISHED |
| Object | Principate |
—
|
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: Principate | Statement: [Roman magistracy, continuedInModifiedFormDuring, Principate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuedInModifiedFormDuring Context triple: [Roman magistracy, continuedInModifiedFormDuring, Principate]
-
A.
laterModification
chosen
Indicates that one entity is a modification or revision that occurs after another in time.
-
B.
continuedIntoPeriod
Indicates that an action, state, or relationship that began earlier persisted without interruption into a specified later time period.
-
C.
replacedDuring
Indicates that one entity took the place of another entity during a specified time period or interval.
-
D.
continuedBy
Indicates that one entity carries on, extends, or resumes the activity, process, or sequence initiated by another entity.
-
E.
amendedFor
Indicates that one entity has been modified or revised specifically to address, correct, or accommodate another entity.
- 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_69bd4636f1648190a701445c2fcd9c17 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd5829cc34819086ad2ae58446502e |
completed | March 20, 2026, 2:22 p.m. |
| PD | Predicate disambiguation | batch_69bd52254c648190a5144cfe8fa7e409 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.