Triple
T35971097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Изборская крепость |
E1040285
|
entity |
| Predicate | использованиеПослеУтратыЗначения |
P184297
|
FINISHED |
| Object | местное административное и жилое поселение |
—
|
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: местное административное и жилое поселение | Statement: [Изборская крепость, использованиеПослеУтратыЗначения, местное административное и жилое поселение]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: использованиеПослеУтратыЗначения Context triple: [Изборская крепость, использованиеПослеУтратыЗначения, местное административное и жилое поселение]
-
A.
subsequentUse
Indicates that one entity is used, applied, or consumed after another entity in time or sequence.
-
B.
используетсяС
Indicates that something is used together with or by means of another entity.
-
C.
ceasedToBeUsed
Indicates that something that was previously in use has stopped being used from a certain point in time onward.
-
D.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
E.
usedVia
Indicates that an entity performs or achieves something by means of, or through the use of, another entity or mechanism.
- F. None of above. chosen
Provenance (4 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_69f76e27758c81909b711cf38a130aaf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ad15f3b88190b7c9742a734fec5f |
completed | May 3, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7acad20388190b9b10270ca9bdfbc |
completed | May 3, 2026, 8:14 p.m. |
Created at: May 3, 2026, 4:07 p.m.