Triple
T29179697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paratethys Sea |
E739711
|
entity |
| Predicate | coveredPresentDay |
P5597
|
FINISHED |
| Object | Central Europe |
—
|
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: Central Europe | Statement: [Paratethys Sea, coveredPresentDay, Central Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coveredPresentDay Context triple: [Paratethys Sea, coveredPresentDay, Central Europe]
-
A.
coveredSince
Indicates that one entity has been under the protection, applicability, or effect of another entity continuously starting from a specified point in time.
-
B.
landedInPresentDay
Indicates that an entity arrived or came to rest in a location corresponding to where that place exists in the present day.
-
C.
partOfPresentDay
Indicates that one entity is a component, region, or subset of what constitutes the other entity in its current, modern-day form.
-
D.
covered
chosen
Indicates that one entity lies over or on top of another entity so as to conceal, protect, or obscure it.
-
E.
rediscoveredIn
Indicates that something previously known but lost or forgotten was found or identified again at a particular time or 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 28, 2026, 11:56 a.m.