Triple
T8435095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kars |
E199207
|
entity |
| Predicate | nearbyArchaeologicalSiteType |
P55205
|
FINISHED |
| Object | medieval Armenian city |
—
|
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: medieval Armenian city | Statement: [Kars, nearbyArchaeologicalSiteType, medieval Armenian city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyArchaeologicalSiteType Context triple: [Kars, nearbyArchaeologicalSiteType, medieval Armenian city]
-
A.
hasArchaeologicalSiteType
Indicates that an entity is classified as, or associated with, a specific type or category of archaeological site.
-
B.
heritageSiteTypeNearby
chosen
Indicates that a particular type of heritage site is located in close proximity to the referenced entity.
-
C.
hasNearbyArchaeologicalSite
Indicates that an entity is located close to or in the vicinity of an archaeological site.
-
D.
notableArchaeologicalSite
Indicates that a place is recognized as an archaeologically significant site, typically due to important historical remains, artifacts, or research findings.
-
E.
hasArchaeologicalSitesFrom
Indicates that an entity contains or is associated with archaeological sites dating from a specified time period or era.
- 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_69ca8314cd6c8190a6b8c2a1096e18f3 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe30fba4081908bfdef3faf5baceb |
completed | March 31, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69cbd0ec200c8190b0299e2b0b4bdcc2 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:08 p.m.