Triple
T9109114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USGS Lake Placid |
E218549
|
entity |
| Predicate | showsContourLines |
P10300
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [USGS Lake Placid, showsContourLines, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showsContourLines Context triple: [USGS Lake Placid, showsContourLines, yes]
-
A.
mapColorLines
Indicates a relationship where colors are assigned or associated with specific lines, such as mapping each line to a particular color.
-
B.
hasStraightLines
Indicates that the related entity possesses or is characterized by straight, non-curved lines.
-
C.
topographicMap
chosen
Indicates a mapping relationship where a representation shows the physical terrain features and elevation contours of a geographic area.
-
D.
hasTopographicContext
Indicates that one entity is related to or characterized by a particular topographic or physical landscape context.
-
E.
hasLandscapeFeatures
Indicates that an entity possesses or includes specific landscape-related characteristics or elements.
- 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_69ca83db7448819090d0a5de842ef2ac |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca845d9b0819084230e7cdd92dee0 |
completed | April 1, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69cc65fe5be081909d4470d6317b14a6 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:16 p.m.