Triple
T29185173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caesar of the Western Roman Empire |
E739847
|
entity |
| Predicate | continuedUseAfter |
P180523
|
FINISHED |
| Object | Constantinian dynasty |
—
|
NE NERFINISHED |
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: Constantinian dynasty | Statement: [Caesar of the Western Roman Empire, continuedUseAfter, Constantinian dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuedUseAfter Context triple: [Caesar of the Western Roman Empire, continuedUseAfter, Constantinian dynasty]
-
A.
eraOfContinuedUse
Indicates a time period during which something remains in ongoing, active use or operation.
-
B.
subsequentUse
Indicates that one entity is used, applied, or consumed after another entity in time or sequence.
-
C.
continuedThrough
Indicates that an event, state, or process persisted without interruption across or beyond a specified point, period, or boundary.
-
D.
mainUseContinued
Indicates that the primary use or function of something persists or remains in effect over a subsequent period.
-
E.
continuesCourseOf
Indicates that one course, treatment, or process is carried on, extended, or maintained as a direct continuation of another.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69f7431aac148190bb6aac59817c174a |
completed | May 3, 2026, 12:44 p.m. |
Created at: April 28, 2026, 11:59 a.m.