Triple
T32914659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tetschen Altar |
E841971
|
entity |
| Predicate | locatedInCountryAtCommissionTime |
P103056
|
FINISHED |
| Object | Bohemia |
E30190
|
NE 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: Bohemia | Statement: [Tetschen Altar, locatedInCountryAtCommissionTime, Bohemia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInCountryAtCommissionTime Context triple: [Tetschen Altar, locatedInCountryAtCommissionTime, Bohemia]
-
A.
countryOfCommission
Indicates the country in which an action, work, or project was formally commissioned or authorized.
-
B.
locatedInCurrentCountry
Indicates that an entity is situated within the geographic boundaries of the country in which it is presently found.
-
C.
locationCountryAtTheTime
chosen
Indicates that an entity was located in a specified country during a particular time or time period.
-
D.
locatedInCountryDuringEvent
Indicates that an entity was situated within a specific country for the duration or at the time of a particular event.
-
E.
positionInceptionCountry
Indicates the country in which a given position, role, or office was originally established or came into existence.
- F. None of above.
Provenance (4 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0337c7389c8190b71d27b8eb8daf9a |
completed | May 12, 2026, 2:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34c67cf46081908af468d6b4eefea6 |
completed | June 19, 2026, 4:33 a.m. |
| PD | Predicate disambiguation | batch_6a0335b7b1588190b02a0ce6a08704aa |
completed | May 12, 2026, 2:14 p.m. |
Created at: May 1, 2026, 1:19 a.m.