Triple
T27999105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slovak Rome |
E707097
|
entity |
| Predicate | appliesToCityKnownFor |
P144057
|
FINISHED |
| Object | church architecture |
—
|
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: church architecture | Statement: [Slovak Rome, appliesToCityKnownFor, church architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToCityKnownFor Context triple: [Slovak Rome, appliesToCityKnownFor, church architecture]
-
A.
isInTownKnownFor
chosen
Indicates that one entity is located in a town that is notable or distinguished for the other entity.
-
B.
cityRecognizedBy
Indicates that a city has been formally acknowledged, certified, or granted status by a particular authority, organization, or governing body.
-
C.
notableCityIncluded
Indicates that a notable or significant city is contained within, or is part of, a larger geographic or administrative entity.
-
D.
primaryCityLandmarkOf
Indicates that a landmark is a principal or defining landmark associated with a specific city.
-
E.
hasFamousCity
Indicates that an entity possesses or is associated with a city that is widely recognized or renowned.
- 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_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: April 27, 2026, 7:55 p.m.