Triple
T37650227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MCC-VD |
E937152
|
entity |
| Predicate | MCCMeans |
P37398
|
FINISHED |
| Object | Moscow Central Circle |
—
|
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: Moscow Central Circle | Statement: [MCC-VD, MCCMeans, Moscow Central Circle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MCCMeans Context triple: [MCC-VD, MCCMeans, Moscow Central Circle]
-
A.
CMeans
chosen
Indicates that one concept or entity conveys, expresses, or serves as the means by which another concept or entity is understood or represented.
-
B.
clusterCriterion
Indicates the rule or condition used to group items together into a cluster based on shared characteristics or similarity.
-
C.
clusterConcentration
Indicates how densely the elements within a cluster are packed or distributed relative to one another.
-
D.
clusterStructure
Indicates that multiple entities are organized into a cluster, specifying how the elements are grouped and related within that clustered arrangement.
-
E.
maximumClusterCount
Indicates the highest number of clusters that are allowed or can be formed in a given context.
- 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa1321b48190af92a3e7ec24ec5b |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.