Triple
T21395477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ovech Glacier |
E527767
|
entity |
| Predicate | relatedMap |
P143808
|
FINISHED |
| Object | L.L. Ivanov topographic map of Smith Island |
—
|
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: L.L. Ivanov topographic map of Smith Island | Statement: [Ovech Glacier, relatedMap, L.L. Ivanov topographic map of Smith Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedMap Context triple: [Ovech Glacier, relatedMap, L.L. Ivanov topographic map of Smith Island]
-
A.
relatedPass
Indicates that one pass is associated with or connected to another pass in some relevant way.
-
B.
relatedField
Indicates that one field, topic, or area of study is connected or relevant to another in subject matter or application.
-
C.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
D.
mapped
Indicates that one entity has been associated, corresponded, or linked systematically to another according to some defined mapping or alignment.
-
E.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
- 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_69e0b51ff3748190935c0a513c62a12b |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69ee62ce3c5c81909e1e584e2f6667c8 |
completed | April 26, 2026, 7:09 p.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 5:13 p.m.