Triple
T31594485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ethiopian canon law |
E806184
|
entity |
| Predicate | historicalCorePeriod |
P4928
|
FINISHED |
| Object | late antique period |
—
|
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: late antique period | Statement: [Ethiopian canon law, historicalCorePeriod, late antique period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalCorePeriod Context triple: [Ethiopian canon law, historicalCorePeriod, late antique period]
-
A.
historicalDocumentationPeriod
Indicates the time span during which something is documented or recorded in historical sources.
-
B.
historicalCoreOf
Indicates that one entity constitutes the original or most historically significant central part of another entity.
-
C.
historicalPartitionPeriod
Indicates that an entity existed, occurred, or is relevant during a specific historical period of territorial partition.
-
D.
historicalIntroductionPeriod
Indicates the time period during which something was first introduced or came into use in a historical context.
-
E.
historicalPeriodOfSignificance
chosen
Indicates the time period during which an entity is considered to have had its most important or influential historical impact.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff4de66ba481908e7184b3cf9d4d2d |
completed | May 9, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69ff4c702a5881909c6684c74807e945 |
completed | May 9, 2026, 3:02 p.m. |
Created at: April 30, 2026, 10:29 p.m.