Triple
T24190971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | princes of Sirmium |
E599693
|
entity |
| Predicate | regionHistoricallyLinked |
P63734
|
FINISHED |
| Object | Pannonia |
—
|
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: Pannonia | Statement: [princes of Sirmium, regionHistoricallyLinked, Pannonia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionHistoricallyLinked Context triple: [princes of Sirmium, regionHistoricallyLinked, Pannonia]
-
A.
historicallyLinked
Indicates that two entities are connected through a shared or related historical event, period, or development.
-
B.
regionHistory
chosen
Indicates that there exists a historical or past association between a subject and a specific geographic or administrative region.
-
C.
historicalRegionAssociation
Indicates an association where an entity is or was located in, part of, or otherwise related to a specific historical region.
-
D.
historicalRegionCorrespondsTo
Indicates that a historical region matches or aligns with a specific region, territory, or administrative unit in terms of location, extent, or identity.
-
E.
regionHistoricalName
Indicates that a region has been known by a particular historical name during some past period.
- 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_69e288cdc8b88190bf2f835d3cb4ca28 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:35 p.m.