Triple
T3205647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carolingian minuscule |
E67153
|
entity |
| Predicate | eventuallySupersededBy |
P101
|
FINISHED |
| Object | Gothic script |
—
|
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: Gothic script | Statement: [Carolingian minuscule, eventuallySupersededBy, Gothic script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventuallySupersededBy Context triple: [Carolingian minuscule, eventuallySupersededBy, Gothic script]
-
A.
wasSupersededBy
chosen
Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
-
B.
supersededInPrecisionBy
Indicates that one entity’s level of precision has been replaced or overtaken by another entity’s greater precision.
-
C.
supersededInCentury
Indicates that one entity has been replaced or rendered obsolete by another during a specified century.
-
D.
cededTo
Indicates that control, ownership, or authority over something was formally transferred from one entity to another.
-
E.
cededFrom
Indicates that control, ownership, or sovereignty over something was transferred away from a source entity to another entity, typically through a formal or legal act of cession.
- 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_69ad8589bd988190afa7ed2bdffb7b33 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaa559848819082d1e61f586278dd |
completed | March 8, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69ad9e078f7c8190813d9fcb4f5071fb |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.