Triple
T23301114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian health services |
E590304
|
entity |
| Predicate | primaryFinancingSource |
P145631
|
FINISHED |
| Object | general taxation |
—
|
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: general taxation | Statement: [Norwegian health services, primaryFinancingSource, general taxation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFinancingSource Context triple: [Norwegian health services, primaryFinancingSource, general taxation]
-
A.
secondaryFundingSource
Indicates that an entity has an additional, non-primary source of financial support or funding.
-
B.
hasPrimaryFundingSource
chosen
Indicates that an entity receives its main or principal financial support from a specified funding source.
-
C.
loanSource
Indicates that one entity is the origin or provider of a loan extended to another entity.
-
D.
fundingSourceProposed
Indicates that a particular source of funding has been suggested or put forward to finance an activity, project, or entity.
-
E.
sourceOfCapital
Indicates the origin or provider from which an entity obtains its financial capital or funding.
- 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_69e25d1c0ecc8190a355aa229f06d0e0 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196d37fd08190ad2d199c54324c02 |
completed | April 29, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 5:04 p.m.