Triple
T36372142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moskovsky District |
E895789
|
entity |
| Predicate | hasMajorCharacteristic |
P99469
|
FINISHED |
| Object | Soviet-era 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: Soviet-era architecture | Statement: [Moskovsky District, hasMajorCharacteristic, Soviet-era architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorCharacteristic Context triple: [Moskovsky District, hasMajorCharacteristic, Soviet-era architecture]
-
A.
hasMajor
Indicates that an entity (typically a person or student) has a specific primary field of academic study or specialization.
-
B.
hasHumanCharacteristic
Indicates that an entity possesses a trait, quality, or behavior typically associated with humans.
-
C.
subjectHasCharacteristic
chosen
Indicates that a subject possesses, exhibits, or is defined by a particular characteristic or attribute.
-
D.
hasParticularNotableCharacteristic
Indicates that an entity possesses a specific, noteworthy characteristic or quality that distinguishes it in some relevant context.
-
E.
hasMajorCategory
Indicates that something is associated with or classified under a primary, overarching category.
- 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_69f76e5115588190ad8738860b7bc68b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0337c7389c8190b71d27b8eb8daf9a |
completed | May 12, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_6a0335b7b1588190b02a0ce6a08704aa |
completed | May 12, 2026, 2:14 p.m. |
Created at: May 3, 2026, 4:10 p.m.