Triple
T37941927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Тимирязевская |
E946510
|
entity |
| Predicate | система |
P730
|
FINISHED |
| Object | Московский метрополитен |
—
|
NE NERFINISHED |
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.
system
chosen
Indicates that an entity functions as or belongs to a structured, organized set of components or processes that operate together as a system.
-
B.
computerSystem
Indicates a relationship where an entity functions as or is classified as a computer system, typically comprising hardware, software, and related components that operate together.
-
C.
primarySystem
Indicates that one system is designated as the main or most important system in relation to another system or context.
-
D.
systemType
Indicates the classification or category of a system that an entity belongs to or operates as.
-
E.
softwareSystem
Indicates a relationship where an entity functions as, or is classified as, a software system.
- 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.