Triple
T663846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kraków |
E12815
|
entity |
| Predicate | hasMedievalCore |
P16505
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Kraków, hasMedievalCore, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMedievalCore Context triple: [Kraków, hasMedievalCore, yes]
-
A.
medievalState
Indicates that an entity functioned as a state or political unit during the medieval historical period.
-
B.
historicalCoreOf
chosen
Indicates that one entity constitutes the original or most historically significant central part of another entity.
-
C.
isFeudal
Indicates that one entity holds a feudal relationship to another, typically involving hierarchical obligations such as land tenure, service, or allegiance.
-
D.
attestedUntilCentury
Indicates the latest century up to which the existence or use of something is historically documented or evidenced.
-
E.
hasHeritage
Indicates that an entity possesses or is associated with a particular cultural, ethnic, or ancestral background.
- 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_69a493355dec819098d4244b2fa34885 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49fd1f0ec819087003d30bbab2fa6 |
completed | March 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69a49d16cff881908c8d2c3fe4d1d6fb |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.