Triple
T16531937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USGS National Map |
E401587
|
entity |
| Predicate | dataTheme |
P123923
|
FINISHED |
| Object | topographic data |
—
|
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: topographic data | Statement: [USGS National Map, dataTheme, topographic data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataTheme Context triple: [USGS National Map, dataTheme, topographic data]
-
A.
themeFor
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
B.
featuresThemeType
Indicates that something (such as a work, event, or item) has or is characterized by a particular type of theme.
-
C.
themeInspiration
Indicates that one entity serves as the creative source or conceptual basis that inspires or shapes the theme expressed in another entity.
-
D.
themeExamples
Indicates that the related entity serves as an example or illustration of the theme expressed by the subject.
-
E.
graphicsTheme
Indicates the visual style or design motif that characterizes how something is graphically presented or themed.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32ed8075c81908ff47396879abd0c |
completed | April 18, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:15 a.m.