Triple
T19012540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow State University of Railway Engineering (historical building area) |
E465263
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic campus complex |
C35648
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: historic campus complex Context triple: [Moscow State University of Railway Engineering (historical building area), instanceOf, historic campus complex]
-
A.
historic campus area
chosen
A historic campus area is a designated portion of an educational institution’s grounds that preserves and showcases buildings, landscapes, and landmarks of significant architectural, cultural, or institutional heritage.
-
B.
historic school
A historic school is an educational institution of notable age and significance, preserved or recognized for its architectural, cultural, or social importance in the history of education.
-
C.
former campus site
A former campus site is a location that once hosted an educational institution’s campus but has since been repurposed, abandoned, or redeveloped for other uses.
-
D.
historic institution
A historic institution is an established organization or structure that has played a significant, enduring role in society over time and is recognized for its cultural, political, or social legacy.
-
E.
historic establishment
A historic establishment is a long-standing place of business or institution recognized for its significant role, continuity, and influence in a particular community or period of history.
- F. None of above.
Provenance (1 batch)
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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:02 p.m.