Triple
T3167640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cartographic Services |
E66249
|
entity |
| Predicate | hasBrandEvolution |
P45325
|
FINISHED |
| Object | rebranded as MapQuest |
—
|
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: rebranded as MapQuest | Statement: [Cartographic Services, hasBrandEvolution, rebranded as MapQuest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBrandEvolution Context triple: [Cartographic Services, hasBrandEvolution, rebranded as MapQuest]
-
A.
brandEvolution
chosen
Indicates how a brand’s identity, positioning, or attributes change and develop over time.
-
B.
formerBrand
Indicates that an entity was previously used or recognized as a brand for another entity but is no longer its current brand.
-
C.
hasFormerLogo
Indicates that an entity is associated with a logo it used in the past but no longer uses.
-
D.
hasBrandName
Indicates that an entity is associated with or identified by a specific brand name.
-
E.
introducedAsBrandBy
Indicates that one entity was presented or launched to the public or a market as a brand by another entity.
- 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_69ad8585d7988190af37365331093ccd |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada6457acc8190b2b9acbd1cfcdb91 |
completed | March 8, 2026, 4:39 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfe0a948190928f2201d671c654 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.