Triple
T32119913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ljusne |
E820339
|
entity |
| Predicate | hasPrimaryResourceBase |
P56483
|
FINISHED |
| Object | forests of Hälsingland |
—
|
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: forests of Hälsingland | Statement: [Ljusne, hasPrimaryResourceBase, forests of Hälsingland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryResourceBase Context triple: [Ljusne, hasPrimaryResourceBase, forests of Hälsingland]
-
A.
hasResourceBase
chosen
Indicates that one entity possesses, is founded on, or derives from another entity serving as its fundamental resource or base.
-
B.
hasPrimary
Indicates that one entity is designated as the main or most important instance (the primary) in relation to another entity.
-
C.
hasPrimaryURL
Indicates that an entity is associated with its main or canonical web address (URL).
-
D.
hasPrimaryFeature
Indicates that an entity possesses a main or most characteristic feature that defines or distinguishes it.
-
E.
hasPrimarySystem
Indicates that an entity is associated with or operates under a main or principal system among potentially multiple systems.
- 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_69f34902d42c819083a8e6bba9a8bb9a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a00ada2903481908b28ce55ef97a6c2 |
completed | May 10, 2026, 4:09 p.m. |
| PD | Predicate disambiguation | batch_6a00ad5d23788190b3f9e2de761d39bb |
completed | May 10, 2026, 4:07 p.m. |
Created at: May 1, 2026, 12:28 a.m.