Triple
T9533474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prospekt Mira (Koltsevaya Line) |
E229952
|
entity |
| Predicate | hasHallType |
P73175
|
FINISHED |
| Object | three-vaulted pylon hall |
—
|
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: three-vaulted pylon hall | Statement: [Prospekt Mira (Koltsevaya Line), hasHallType, three-vaulted pylon hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHallType Context triple: [Prospekt Mira (Koltsevaya Line), hasHallType, three-vaulted pylon hall]
-
A.
hasMainHallType
Indicates the specific category or kind of main hall associated with an entity.
-
B.
hasTicketHall
Indicates that a place or facility includes or is equipped with a designated ticket hall area for purchasing or validating tickets.
-
C.
hasStationHall
chosen
Indicates that one entity (typically a station) includes or is associated with a station hall area as part of its structure or facilities.
-
D.
hasHotelType
Indicates that a hotel is classified as belonging to a specific type or category (e.g., resort, boutique, hostel).
-
E.
hasMainHall
Indicates that an entity possesses or includes a primary or central hall as a significant internal space.
- 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_69ca8479934c81908006d0e6e970ae05 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98c9fef88190beb291b41ee26066 |
completed | April 1, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69cca56c44f88190a54a5d2a133bb07e |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 8 p.m.