Triple
T559484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Orkney Islands |
E13415
|
entity |
| Predicate | originallyUsedFor |
P11902
|
FINISHED |
| Object | sealing |
—
|
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: sealing | Statement: [South Orkney Islands, originallyUsedFor, sealing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyUsedFor Context triple: [South Orkney Islands, originallyUsedFor, sealing]
-
A.
historicallyUsedFor
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
B.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
C.
originallyDevelopedFor
chosen
Indicates that something was first created, designed, or produced with the primary purpose of serving a particular use, user group, context, or application.
-
D.
firstUsedFor
Indicates that one entity was the earliest or original thing for which another entity was used or applied.
-
E.
usedPrimarilyIn
Indicates that something is mainly or most commonly employed within a particular context, domain, or purpose.
- 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_69a4933edcf08190b35ecfd6014caee6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a499e13694819087a236bffa6601a9 |
completed | March 1, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69a494befb8481908bb4e2e9f31e343b |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.