Triple
T35957718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prehistoric Estonia |
E1039914
|
entity |
| Predicate | hasEndInPeriod |
P118268
|
FINISHED |
| Object | Early Middle Ages |
—
|
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: Early Middle Ages | Statement: [Prehistoric Estonia, hasEndInPeriod, Early Middle Ages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEndInPeriod Context triple: [Prehistoric Estonia, hasEndInPeriod, Early Middle Ages]
-
A.
isSetInTimePeriod
Indicates that an event, story, or situation takes place within a specified time period.
-
B.
recordedInPeriodEnd
Indicates that an event, transaction, or record is logged as occurring within the closing portion of a specified time period.
-
C.
hasPeriodOf
Indicates that one entity possesses, experiences, or is associated with a specific span or interval of time.
-
D.
hasEnd
Indicates that one entity serves as the terminal point, boundary, or conclusion of another entity or process.
-
E.
hasTemporalEnd
chosen
Indicates that an event, state, or process concludes or terminates at a specific point or interval in time.
- 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_69f76e26b21081909fd9ffb3aff6c77a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
Created at: May 3, 2026, 4:07 p.m.