Triple
T1453749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byzantium |
E31350
|
entity |
| Predicate | roleAfterRefounding |
P28773
|
FINISHED |
| Object | capital of the Roman Empire |
—
|
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: capital of the Roman Empire | Statement: [Byzantium, roleAfterRefounding, capital of the Roman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAfterRefounding Context triple: [Byzantium, roleAfterRefounding, capital of the Roman Empire]
-
A.
refoundedBy
Indicates that an entity was re-established or reconstituted by another entity after a period of inactivity, dissolution, or significant change.
-
B.
governingBodyLaterKnownAs
Indicates that the governing body of an entity was later renamed or became known by a different official title.
-
C.
namedAfterSince
Indicates that one entity has borne the name of another entity starting from a specific point in time.
-
D.
formerAdministeredBy
Indicates that an entity was previously administered or managed by another entity, but is no longer under that administration.
-
E.
roleBeforeQuietRevolution
Indicates that an entity held a particular role or status prior to the Quiet Revolution period.
- 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_69a499171a28819085b993a3ac78e363 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c57e82d48190a30a4512f39f5de0 |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c47cdbd0819092022344a2f4ad7b |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c55508948190922aee3230a4323e |
completed | March 1, 2026, 11:01 p.m. |
Created at: March 1, 2026, 8 p.m.