Triple
T37172586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gunnerside |
E920953
|
entity |
| Predicate | nationalityOfMainForce |
P195884
|
FINISHED |
| Object | Norwegian |
—
|
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: Norwegian | Statement: [Gunnerside, nationalityOfMainForce, Norwegian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nationalityOfMainForce Context triple: [Gunnerside, nationalityOfMainForce, Norwegian]
-
A.
nationalityOfPersonnel
Indicates the country or countries to which the personnel involved in an activity, organization, or context belong by citizenship or national affiliation.
-
B.
countryOfAllegiance
Indicates the country to which an entity owes loyalty, support, or official allegiance.
-
C.
nationalityAtLaunch
Indicates the country or national affiliation associated with an entity at the specific time it was launched.
-
D.
memberNationForces
chosen
Indicates that the forces belong to, are contributed by, or are under the authority of a particular member nation.
-
E.
countryForWhichFought
Indicates the country on whose behalf or under whose authority an entity participated in a conflict or war.
- 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_69f76ea16f288190b445aa1604d996f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
Created at: May 3, 2026, 4:15 p.m.