Triple
T27999111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slovak Rome |
E707097
|
entity |
| Predicate | appliesToCityWithStatus |
P174178
|
FINISHED |
| Object | major religious center in Slovakia |
—
|
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: major religious center in Slovakia | Statement: [Slovak Rome, appliesToCityWithStatus, major religious center in Slovakia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToCityWithStatus Context triple: [Slovak Rome, appliesToCityWithStatus, major religious center in Slovakia]
-
A.
cityStatusAppliesTo
chosen
Indicates that a particular city status or designation is applicable to a given city or urban entity.
-
B.
hasCityStatusFor
Indicates that an entity holds official city status within the jurisdiction or context of another entity.
-
C.
impliesStatusOfCity
Indicates that one entity suggests, infers, or entails a particular status or condition of a city.
-
D.
supportsCity
Indicates that one entity provides assistance, resources, or backing to a city, helping it function, develop, or achieve its goals.
-
E.
isInCity
Indicates that one entity is located within the geographical boundaries of a specified city.
- 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: April 27, 2026, 7:55 p.m.