Triple
T2396437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow Central Circle |
E47660
|
entity |
| Predicate | circleType |
P37911
|
FINISHED |
| Object | full orbital line around 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: full orbital line around central Moscow | Statement: [Moscow Central Circle, circleType, full orbital line around central Moscow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: circleType Context triple: [Moscow Central Circle, circleType, full orbital line around central Moscow]
-
A.
circles
Indicates that one entity moves around another entity along a roughly circular path or orbit.
-
B.
ringRadius
Indicates the size of a ring by specifying the distance from its center to its outer edge.
-
C.
centeredDisc
Indicates that one disc-shaped object is positioned with its center aligned to a specified reference point or object.
-
D.
cycleType
Indicates the specific kind or category of cycle involved in a repeated or cyclical process or relationship.
-
E.
circumference
Indicates the total length around the boundary of a closed curve, typically a circle, relating a shape to the measure of its perimeter.
- 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_69a88a1c450c81909f61abb8b6863885 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc8c4a8bc819086892a75caac0207 |
completed | March 7, 2026, 6:42 a.m. |
| PD | Predicate disambiguation | batch_69abc5a3825c81909ec6111dfc165453 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abc664317c8190a6bb5a5065c21bde |
completed | March 7, 2026, 6:32 a.m. |
Created at: March 4, 2026, 7:57 p.m.