Triple
T23422077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fram expedition 1893–1896 |
E560683
|
entity |
| Predicate | attemptedFromRegion |
P33091
|
FINISHED |
| Object | near Franz Josef Land |
—
|
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: near Franz Josef Land | Statement: [Fram expedition 1893–1896, attemptedFromRegion, near Franz Josef Land]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attemptedFromRegion Context triple: [Fram expedition 1893–1896, attemptedFromRegion, near Franz Josef Land]
-
A.
isFromRegion
chosen
Indicates that one entity originates from, is associated with, or belongs to a specified geographic region.
-
B.
recipientRegion
Indicates the geographic region that receives or is the destination of a transfer, delivery, or directed action.
-
C.
successRegion
Indicates the geographic or contextual area within which a particular action, process, or outcome is considered successful.
-
D.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
E.
registrationRegion
Indicates the geographic or administrative region in which an entity is officially registered.
- 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_69e2454cb1108190ab21ada5411a7146 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a546c08c8190b57d90e88034eef3 |
completed | April 29, 2026, 6:29 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:46 p.m.