Triple
T11126919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shosse Entuziastov MCC station |
E263162
|
entity |
| Predicate | isOrbitalTo |
P97679
|
FINISHED |
| Object | Moscow city center |
—
|
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: Moscow city center | Statement: [Shosse Entuziastov MCC station, isOrbitalTo, Moscow city center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOrbitalTo Context triple: [Shosse Entuziastov MCC station, isOrbitalTo, Moscow city center]
-
A.
isOrbitalRouteFor
Indicates that one path or trajectory serves as the designated orbital route followed by another object (such as a spacecraft or satellite).
-
B.
isOnOrbital
Indicates that one entity is located on or traveling along the orbital path associated with another entity.
-
C.
onOrbitalRoute
Indicates that one object is currently traveling along or positioned on a defined orbital path around another body.
-
D.
hasOrbitalDirection
Indicates that one celestial body orbits another in a specified directional sense (e.g., prograde or retrograde).
-
E.
hasOrbitalPlane
Indicates that one entity possesses or is associated with a specific orbital plane in which its orbit lies.
- F. None of above. chosen
Provenance (4 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7e82fc5f88190b34c55de3d50f6a7 |
completed | April 9, 2026, 5:55 p.m. |
| PD | Predicate disambiguation | batch_69d7441efe948190ae4ab020121e169d |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d75112eb1c8190ba1dd51e42e8a7e8 |
completed | April 9, 2026, 7:11 a.m. |
Created at: April 8, 2026, 9:28 p.m.