Triple
T11704845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Creeping Winter |
E278211
|
entity |
| Predicate | addsLocation |
P44057
|
FINISHED |
| Object | frozen tundra areas |
—
|
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: frozen tundra areas | Statement: [Creeping Winter, addsLocation, frozen tundra areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsLocation Context triple: [Creeping Winter, addsLocation, frozen tundra areas]
-
A.
additionalLocation
chosen
Indicates that an entity has one or more extra or secondary locations associated with it beyond its primary location.
-
B.
linkedLocation
Indicates that one location is associated or connected to another location in a meaningful way, such as being related, referenced, or contextually tied.
-
C.
connectsLocation
Indicates a relationship where one entity serves as a link or route that joins or provides access between two locations.
-
D.
subjectLocation
Indicates that one entity is located at, in, or near the place or position specified by another entity.
-
E.
setLocation
Indicates assigning or updating the place or position where an entity is located.
- 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a49c8c38819083d83f5fdec52b7f |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a7b30948190b616a9db5c5488d5 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.