Triple
T34543802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maps.me |
E886869
|
entity |
| Predicate | usesMapRendering |
P188915
|
FINISHED |
| Object | vector maps |
—
|
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: vector maps | Statement: [Maps.me, usesMapRendering, vector maps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMapRendering Context triple: [Maps.me, usesMapRendering, vector maps]
-
A.
mapUse
Indicates a relationship where one entity uses, applies, or employs a map (or mapping) to perform an action or achieve a purpose.
-
B.
hasMaps
Indicates that one entity possesses, includes, or provides access to one or more maps associated with another entity.
-
C.
usesMapRectType
Indicates that one entity employs or relies on a specific rectangular map representation or type in its operation or definition.
-
D.
canMap
Indicates that one entity is able to be mapped or transformed systematically into another entity or representation.
-
E.
mapDisplay
Indicates that something is being visually represented or shown on a map interface.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fbaf18085481908c774e8f8bbb9a41 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbaebbb7f88190b4edfd9b83550aad |
completed | May 6, 2026, 9:12 p.m. |
Created at: May 1, 2026, 2:02 a.m.