Triple
T9827068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Croton Reservoir |
E238682
|
entity |
| Predicate | isMappedAs |
P42815
|
FINISHED |
| Object | lake on topographic maps |
—
|
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: lake on topographic maps | Statement: [Croton Reservoir, isMappedAs, lake on topographic maps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMappedAs Context triple: [Croton Reservoir, isMappedAs, lake on topographic maps]
-
A.
hasOfficialMapping
Indicates that there exists an established, authoritative correspondence or translation between one entity and another.
-
B.
hasMappingProperty
Indicates that there exists a defined correspondence or association between elements of one set, structure, or representation and elements of another.
-
C.
mappedUsing
Indicates that one entity is associated or transformed into another entity through a specified mapping method or mechanism.
-
D.
hasMapReference
Indicates that an entity is associated with a specific map or map location reference.
-
E.
hasMapType
chosen
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_69ca84e0dd1881909800765d1e21f735 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb324e7848190b9424a78ca653afe |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e30bc08190816c0a6d29c21b0f |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:32 p.m.