Triple
T10758594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Map of Virginia |
E253763
|
entity |
| Predicate | mapsRegion |
P33924
|
FINISHED |
| Object | Atlantic coast of North America |
—
|
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: Atlantic coast of North America | Statement: [A Map of Virginia, mapsRegion, Atlantic coast of North America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapsRegion Context triple: [A Map of Virginia, mapsRegion, Atlantic coast of North America]
-
A.
mapRegion
chosen
Indicates a relationship where a map or mapping system corresponds to, covers, or is associated with a specific geographic or logical region.
-
B.
exportRegion
Indicates the region or geographic area from which goods, services, or resources are exported.
-
C.
routeRegion
Indicates that a route is located within, passes through, or is associated with a particular geographic region.
-
D.
placeRegion
Indicates that a place is located within, or is part of, a larger geographic or administrative region.
-
E.
isRegion
Indicates that one entity functions as a geographic or administrative region associated with 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d72ea107a48190b6b92bb0df03e517 |
completed | April 9, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69d6f311529c819080ca5493d55d6050 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:15 p.m.