Triple
T31781991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Požarevac |
E811226
|
entity |
| Predicate | nearbyArchaeologicalPeriod |
P47576
|
FINISHED |
| Object | Roman Empire |
—
|
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: Roman Empire | Statement: [Požarevac, nearbyArchaeologicalPeriod, Roman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyArchaeologicalPeriod Context triple: [Požarevac, nearbyArchaeologicalPeriod, Roman Empire]
-
A.
nearbyArchaeologicalCulture
Indicates that one archaeological culture is geographically close to another archaeological culture.
-
B.
hasArchaeologicalRemainsFromPeriod
chosen
Indicates that an entity contains or preserves archaeological remains originating from a specified historical period.
-
C.
nearAncientRegion
Indicates that one entity is located close to, or in the immediate vicinity of, a specified ancient geographical region.
-
D.
archaeologicalRegions
Indicates a relationship where specific areas are designated or recognized as regions of archaeological interest, activity, or significance.
-
E.
hasNearbyArchaeologicalSite
Indicates that an entity is located close to or in the vicinity of an archaeological site.
- 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_69f348e544a48190ab6e700b05f6438c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: April 30, 2026, 11:36 p.m.