Triple
T2471388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Renovatio imperii Romanorum |
E55381
|
entity |
| Predicate | firstSignificantUseCentury |
P16875
|
FINISHED |
| Object | 8th 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: 8th century | Statement: [Renovatio imperii Romanorum, firstSignificantUseCentury, 8th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSignificantUseCentury Context triple: [Renovatio imperii Romanorum, firstSignificantUseCentury, 8th century]
-
A.
introducedInCentury
Indicates the century during which something (such as an idea, technology, practice, or entity) was first introduced or came into use.
-
B.
developedSinceCentury
Indicates that something began to be developed or came into existence starting from a specified century onward.
-
C.
usedInCentury
chosen
Indicates that something (such as an object, practice, or concept) was in use during a specified century.
-
D.
discoveredInCentury
Indicates that an entity was discovered during a specific century.
-
E.
formulatedInCentury
Indicates that something (such as an idea, theory, or work) was originally created or developed during a specified century.
- 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_69ab49e3622c8190ad22afa2c4fbb807 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd1eb3be481908fa7c6b8f1c78209 |
completed | March 7, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69abd0b5e3d481909a5cbc4a96edd24f |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:44 p.m.