Triple
T32394844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Istrinsky District |
E827774
|
entity |
| Predicate | hasHistoricalTowns |
P43430
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Istrinsky District, hasHistoricalTowns, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalTowns Context triple: [Istrinsky District, hasHistoricalTowns, true]
-
A.
containsHistoricTown
chosen
Indicates that one entity geographically includes or encompasses a town that has recognized historical significance.
-
B.
hasHistoricTownRights
Indicates that an entity possesses officially granted historic town rights, typically conferring a traditional legal or municipal status as a town.
-
C.
historicalMainTown
Indicates that one place served as the primary or principal town for another place during a specific historical period.
-
D.
hasHistoricCity
Indicates that an entity possesses, contains, or is associated with a city recognized for its historical significance.
-
E.
hasHistoricVillagesAlong
Indicates that a route, path, or geographic feature has historic villages located along its course or in close proximity to it.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe779248c081909f0ed1a2a0df23db |
completed | May 8, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69fe76eaf6d48190998bc7168749cc42 |
completed | May 8, 2026, 11:51 p.m. |
Created at: May 1, 2026, 12:52 a.m.