Triple
T17657282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heimefront Range |
E440157
|
entity |
| Predicate | exploredInPeriod |
P23375
|
FINISHED |
| Object | 1949–1952 |
—
|
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: 1949–1952 | Statement: [Heimefront Range, exploredInPeriod, 1949–1952]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exploredInPeriod Context triple: [Heimefront Range, exploredInPeriod, 1949–1952]
-
A.
exploredDuring
chosen
Indicates that an entity was explored or investigated within the time frame or context of a specified event or period.
-
B.
expeditionPeriod
Indicates the time span or duration during which an expedition takes place.
-
C.
appearedThroughPeriod
Indicates that an entity was present or manifested continuously or recurrently throughout a specified time period.
-
D.
appearsInTimePeriod
Indicates that an entity is present, active, or occurs within a specified time period.
-
E.
exploredWith
Indicates that one entity explored something together with another entity as companions or partners in the exploration.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46ea2b3308190b9ad752728d98856 |
completed | April 19, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69e3cddc87188190ac2f049b86038676 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 9:27 a.m.