Triple
T15331939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haugesunder |
E366555
|
entity |
| Predicate | spelledInNynorsk |
P49477
|
FINISHED |
| Object | Haugesunder |
—
|
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: Haugesunder | Statement: [Haugesunder, spelledInNynorsk, Haugesunder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spelledInNynorsk Context triple: [Haugesunder, spelledInNynorsk, Haugesunder]
-
A.
hasNynorskUsage
Indicates that something is used or expressed in the Norwegian Nynorsk written standard.
-
B.
hasNynorskForm
chosen
Indicates that one linguistic form is the corresponding Nynorsk (Norwegian Nynorsk) version of another form.
-
C.
hasOfficialNameInNorwegianNynorsk
Indicates that an entity has an official name expressed in the Norwegian Nynorsk language.
-
D.
originalSpelling
Indicates that one entity provides the initial or historically first-used spelling form of another entity’s name or term.
-
E.
hasNameInNorwegian
Indicates that an entity is associated with a specific name expressed in the Norwegian 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e0268608190947a58f559a67717 |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca9659f48190b8661df223ce5078 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:17 a.m.