Triple
T31310627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Framheim |
E798451
|
entity |
| Predicate | hasPrimaryLanguageOfExpedition |
P83252
|
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: [Framheim, hasPrimaryLanguageOfExpedition, Norwegian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryLanguageOfExpedition Context triple: [Framheim, hasPrimaryLanguageOfExpedition, Norwegian]
-
A.
hasLanguageOfExploration
Indicates that an entity uses or is associated with a particular language for exploration, investigation, or discovery activities.
-
B.
hasPrimaryLanguage1
chosen
Indicates that an entity’s main or most commonly used language is the specified language.
-
C.
hasLanguageOfMission
Indicates that an entity (such as a mission or project) is associated with a specific language used for its communication, documentation, or operation.
-
D.
nationalityOfExpedition
Indicates the country or national affiliation associated with a given expedition.
-
E.
hasPrimaryLanguageOfResearch
Indicates that an entity’s main or principal language used for conducting and publishing research is a specified language.
- 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a005be4615c8190a710ab704a46c564 |
completed | May 10, 2026, 10:20 a.m. |
| PD | Predicate disambiguation | batch_6a005b8b1cc08190850a392761b84e74 |
completed | May 10, 2026, 10:18 a.m. |
Created at: April 29, 2026, 9:15 p.m.