Triple
T9860367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annino |
E239693
|
entity |
| Predicate | hasSouthVestibule |
P90939
|
FINISHED |
| Object | located near Varshavskoye Highway |
—
|
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: located near Varshavskoye Highway | Statement: [Annino, hasSouthVestibule, located near Varshavskoye Highway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSouthVestibule Context triple: [Annino, hasSouthVestibule, located near Varshavskoye Highway]
-
A.
hasUndergroundVestibule
Indicates that one entity possesses or includes an underground vestibule space connected to it.
-
B.
hasBasement
Indicates that a building or structure includes a basement level as part of its physical layout.
-
C.
hasNarthex
Indicates that one architectural structure (typically a church) includes or is equipped with a narthex area.
-
D.
hasPorch
Indicates that one entity (typically a building or residence) includes or is equipped with a porch as part of its structure.
-
E.
hasLowerFloor
Indicates that one location, structure, or level includes or is directly connected to a floor situated below another floor.
- 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_69ca84e6493081909cf58c8d42ea856b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3b582cc81909a6d638fe2573c43 |
completed | April 2, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69cd1d7621d48190aa6a6f34399514b0 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd3581a9688190a00cef4c3eebb0ae |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:35 p.m.