Triple
T10192040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Novogireyevo |
E238058
|
entity |
| Predicate | hasMapframe |
P92615
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Novogireyevo, hasMapframe, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMapframe Context triple: [Novogireyevo, hasMapframe, yes]
-
A.
hasMapReference
Indicates that an entity is associated with a specific map or map location reference.
-
B.
hasMapType
Indicates that one entity is associated with a specific type or category of map.
-
C.
hasWorldMap
Indicates that one entity possesses, includes, or is associated with a representation of the entire world’s geography.
-
D.
hasMapState
Indicates that an entity is associated with a particular state or condition of a map (such as its configuration, status, or version).
-
E.
mapsFrom
Indicates that one entity is derived, transformed, or constructed based on data, structure, or content originating from another entity.
- 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_69ca84de1b208190bf17bb305b002605 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdedc4fb808190aae2e4b84be96f83 |
completed | April 2, 2026, 4:17 a.m. |
| PD | Predicate disambiguation | batch_69cd7c8477648190bc55c56aeec507d3 |
completed | April 1, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69cd7edc6cf081909d95859d880a4059 |
completed | April 1, 2026, 8:23 p.m. |
Created at: March 30, 2026, 9:13 p.m.