Triple
T19629788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raduzhny (Vladimir Oblast) |
E471234
|
entity |
| Predicate | hasSettlementAgeCharacteristic |
P64802
|
FINISHED |
| Object | 20th century origin or later |
—
|
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: 20th century origin or later | Statement: [Raduzhny (Vladimir Oblast), hasSettlementAgeCharacteristic, 20th century origin or later]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSettlementAgeCharacteristic Context triple: [Raduzhny (Vladimir Oblast), hasSettlementAgeCharacteristic, 20th century origin or later]
-
A.
hasSettlementCharacteristic
chosen
Indicates that a settlement possesses a specific attribute, feature, or quality.
-
B.
hasSettlementRole
Indicates that an entity holds or is assigned a specific functional role or status within a settlement.
-
C.
containsAge
Indicates that one entity includes or specifies the age value or age-related information of another entity.
-
D.
hasSettlementAround
Indicates that a settlement is located in the surrounding area of a specified place or feature.
-
E.
hasAge
Indicates that an entity possesses a specific age value, typically expressed as a number of time units since its birth or creation.
- 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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e64101a0448190ba19f8917ae85dd6 |
completed | April 20, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.