Triple
T33713084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian counties |
E863794
|
entity |
| Predicate | hasExecutiveBodyType |
P130835
|
FINISHED |
| Object | county executive board |
—
|
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: county executive board | Statement: [Norwegian counties, hasExecutiveBodyType, county executive board]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExecutiveBodyType Context triple: [Norwegian counties, hasExecutiveBodyType, county executive board]
-
A.
executiveBody
Indicates that an entity serves as the executive governing authority or decision-making body for another entity.
-
B.
hasGovernmentalBodyType
chosen
Indicates the specific kind or classification of governmental body that an entity possesses or is associated with.
-
C.
executiveBodyHoused
Indicates that an executive body is physically located or based within a particular building, facility, or premises.
-
D.
governingBodyOfType
Indicates that an entity serves as the official governing body for another entity of a specified type or category.
-
E.
hasGovernmentBody
Indicates that one entity serves as the official governing or administrative body responsible for overseeing or managing another entity.
- 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_69f3498844608190bb8f9b14908d2510 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 1, 2026, 1:43 a.m.