Triple
T24621317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arktikugol |
E609419
|
entity |
| Predicate | legalBasisOfPresence |
P125
|
FINISHED |
| Object | Svalbard Treaty |
—
|
NE NERFINISHED |
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: Svalbard Treaty | Statement: [Arktikugol, legalBasisOfPresence, Svalbard Treaty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalBasisOfPresence Context triple: [Arktikugol, legalBasisOfPresence, Svalbard Treaty]
-
A.
legalBasis
chosen
Indicates the legal rule, authority, or justification under which an action, decision, or status is established or carried out.
-
B.
legalStatusAtArrival
Indicates the legal status or classification an entity held at the time it first arrived at a particular place or jurisdiction.
-
C.
legalStatusInHomeland
Indicates the legal status or classification an entity holds within its country or place of origin.
-
D.
legalStandingBasis
Indicates the legal grounds or justification on which a party’s standing or authority in a legal matter is based.
-
E.
legalStatusInDiaspora
Indicates the legal status or classification an entity holds while residing outside its country or place of origin.
- 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_69e2c4d1d3708190a0f2dc6a3a8523bb |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:32 a.m.