Triple
T16341461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Botanichesky Sad MCC station |
E396813
|
entity |
| Predicate | isOnOrbitalLineAround |
P44046
|
FINISHED |
| Object | central Moscow |
—
|
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: central Moscow | Statement: [Botanichesky Sad MCC station, isOnOrbitalLineAround, central Moscow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnOrbitalLineAround Context triple: [Botanichesky Sad MCC station, isOnOrbitalLineAround, central Moscow]
-
A.
isOnOrbital
Indicates that one entity is located on or traveling along the orbital path associated with another entity.
-
B.
isOrbitalTo
Indicates that one entity moves in a curved, repeating path around another entity under the influence of a central force, typically gravity.
-
C.
onOrbitalRoute
chosen
Indicates that one object is currently traveling along or positioned on a defined orbital path around another body.
-
D.
isOrbitalRouteFor
Indicates that one path or trajectory serves as the designated orbital route followed by another object (such as a spacecraft or satellite).
-
E.
isOrbital
Indicates that one entity moves in a curved, repeating path around another entity due to gravitational or similar central forces.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2da0ad510819082e440f5e2bceada |
completed | April 18, 2026, 1:10 a.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.