Triple
T31308013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USGS Mount Marcy quadrangle |
E798386
|
entity |
| Predicate | hasMapTheme |
P108783
|
FINISHED |
| Object | physical geography |
—
|
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: physical geography | Statement: [USGS Mount Marcy quadrangle, hasMapTheme, physical geography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMapTheme Context triple: [USGS Mount Marcy quadrangle, hasMapTheme, physical geography]
-
A.
hasMaps
Indicates that one entity possesses, includes, or provides access to one or more maps associated with another entity.
-
B.
mapTheme
chosen
Indicates a thematic relationship where a map is associated with, organized by, or visually represents a particular theme or subject.
-
C.
hasOverworldMapStyle
Indicates that an entity is associated with or uses a particular style or format for its overworld map.
-
D.
hasMapframe
Indicates that an entity is associated with an embedded, interactive map frame representation of its geographic location or area.
-
E.
hasMapType
Indicates that one entity is associated with a specific type or category of map.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00119d821c8190874786391b27ef23 |
completed | May 10, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_6a001143fb6881909ac0ae8bfea04351 |
completed | May 10, 2026, 5:01 a.m. |
Created at: April 29, 2026, 9:14 p.m.