Triple
T2006426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coptic language |
E43596
|
entity |
| Predicate | standardizedByCentury |
P4436
|
FINISHED |
| Object | 4th century CE |
—
|
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: 4th century CE | Statement: [Coptic language, standardizedByCentury, 4th century CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardizedByCentury Context triple: [Coptic language, standardizedByCentury, 4th century CE]
-
A.
standardizedInCentury
chosen
Indicates that something was standardized or formally established according to a common norm during a specified century.
-
B.
testCenturies
Indicates that an entity has scored one or more centuries (100+ runs) in test cricket matches.
-
C.
originalCentury
Indicates the century in which something was originally created, produced, or came into existence.
-
D.
approximateStartCentury
Indicates the century in which something is estimated or roughly believed to have begun.
-
E.
ruledFromCentury
Indicates that a ruling or governance relationship is associated with a specific century during which it took place.
- 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_69a88716e9f08190946313fdc949e3cf |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb898795481909920c1a4c4d62c2d |
completed | March 7, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69abb79e63c08190982c8b44a557266f |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.