Triple
T3302288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franklin expedition |
E69362
|
entity |
| Predicate | laterAbandonmentLocation |
P42649
|
FINISHED |
| Object | near King William 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: near King William Island | Statement: [Franklin expedition, laterAbandonmentLocation, near King William Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterAbandonmentLocation Context triple: [Franklin expedition, laterAbandonmentLocation, near King William Island]
-
A.
laterLocation
chosen
Indicates that an entity is located at a specified place at a later time than some reference time or earlier location.
-
B.
abandonedIn
Indicates that one entity was left behind or deserted in the location or context specified by another entity.
-
C.
abandonedBy
Indicates that one entity has been deserted, forsaken, or left behind by another entity that was previously present, responsible, or involved.
-
D.
abandonedReason
Indicates the reason or cause for which something was abandoned, discontinued, or given up.
-
E.
abandonment
Indicates the act of one party leaving, forsaking, or giving up responsibility for another party or thing.
- 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_69ad859e529c8190a404273f53cb487d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0a9450481909f0d630e5593085e |
completed | March 8, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69ada42625308190be257f16a623a410 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.