Triple
T30748527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epte |
E782883
|
entity |
| Predicate | historicalPeriodAsBorder |
P47008
|
FINISHED |
| Object | Middle Ages |
—
|
NE NERFINISHED |
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: Middle Ages | Statement: [Epte, historicalPeriodAsBorder, Middle Ages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPeriodAsBorder Context triple: [Epte, historicalPeriodAsBorder, Middle Ages]
-
A.
settingDepictedPeriod
Indicates the historical or temporal period in which the setting of something (e.g., a work or scene) is depicted.
-
B.
historicBoundaryFor
chosen
Indicates that one entity serves as a historical boundary or border associated with another entity, typically reflecting past territorial or administrative limits.
-
C.
hasNearbyHistoricPeriod
Indicates that one historic period occurs close in time or space to another historic period.
-
D.
historicallyCircumscribedBy
Indicates that one entity’s historical existence, development, or significance is bounded, defined, or delimited by the historical context or period associated with another entity.
-
E.
locatedInHistoricPeriod
Indicates that an entity exists, occurs, or is situated within a specific historic period or era.
- 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff16775a9881909d26dbc1f0ef3e1c |
completed | May 9, 2026, 11:11 a.m. |
| PD | Predicate disambiguation | batch_69ff158e61708190a1c581d0d306cfce |
completed | May 9, 2026, 11:07 a.m. |
Created at: April 29, 2026, 8:38 p.m.