Triple
T7685309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kosovo Museum |
E174099
|
entity |
| Predicate | hasNotablePeriodCovered |
P58089
|
FINISHED |
| Object | prehistoric 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: prehistoric period | Statement: [Kosovo Museum, hasNotablePeriodCovered, prehistoric period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotablePeriodCovered Context triple: [Kosovo Museum, hasNotablePeriodCovered, prehistoric period]
-
A.
timePeriodCoveredTo
Indicates the span or duration of time that is encompassed, addressed, or relevant to a given subject or entity.
-
B.
coversPeriodStart
Indicates that the time span or coverage of one entity begins at, or includes, the specified starting point in time of another entity or period.
-
C.
hasHistoryPeriod
chosen
Indicates that something is associated with, belongs to, or occurs within a specific historical period or era.
-
D.
eligibilityPeriod
Indicates the span of time during which an entity qualifies for or is allowed to receive a particular benefit, service, or status.
-
E.
notableWorkPeriod
Indicates the time span during which an entity produced or was associated with its most significant or well-known works.
- 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_69c6995840408190a19de6c51090f46f |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c706d1f0208190bc5b695aa5736244 |
completed | March 27, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69c70163dea88190ae729df50e63dfd7 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:02 p.m.