Triple
T3167642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cartographic Services |
E66249
|
entity |
| Predicate | pioneeringRoleIn |
P2809
|
FINISHED |
| Object | online mapping |
—
|
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: online mapping | Statement: [Cartographic Services, pioneeringRoleIn, online mapping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pioneeringRoleIn Context triple: [Cartographic Services, pioneeringRoleIn, online mapping]
-
A.
pioneerOf
chosen
Indicates that an entity was among the first to develop, introduce, or significantly advance another entity, concept, or practice.
-
B.
foundingRole
Indicates the specific role or capacity an entity held in the founding or establishment of another entity.
-
C.
notableHistoricalFigureRole
Indicates that an entity is recognized as a historically significant person who played a particular role or held a specific position in history.
-
D.
wasProminentIn
Indicates that an entity was notably active, influential, or widely recognized within a particular field, context, or time period.
-
E.
notableContribution
Indicates that an entity has made a significant, recognized contribution to another entity, field, work, or endeavor.
- 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.