Triple
T20745841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conciliation Boards of Norway |
E510579
|
entity |
| Predicate | hearingPublicity |
P39906
|
FINISHED |
| Object | normally public hearings |
—
|
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: normally public hearings | Statement: [Conciliation Boards of Norway, hearingPublicity, normally public hearings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hearingPublicity Context triple: [Conciliation Boards of Norway, hearingPublicity, normally public hearings]
-
A.
hearsMatters
Indicates that one entity formally considers or listens to issues, cases, or concerns involving another entity.
-
B.
heardBy
Indicates that a sound, message, or communication produced by one entity is perceived or received auditorily by another entity.
-
C.
canHear
Indicates that one entity is able to perceive sounds produced by another entity.
-
D.
sessionPublicity
chosen
Indicates that information about a session is made publicly accessible or promoted to a general audience.
-
E.
mayHear
Indicates that one entity is permitted or able to hear sounds, speech, or audio produced by 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_69e0b4c845e88190b4c5f3ae79291182 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c212b744819089bc1d47a020bd61 |
completed | April 21, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:33 p.m.