Triple
T20706523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Labour Court of Norway |
E508915
|
entity |
| Predicate | primaryPartiesInDisputes |
P83991
|
FINISHED |
| Object | employers |
—
|
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: employers | Statement: [Labour Court of Norway, primaryPartiesInDisputes, employers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryPartiesInDisputes Context triple: [Labour Court of Norway, primaryPartiesInDisputes, employers]
-
A.
hasDisputeParties
chosen
Indicates that a dispute involves the specified parties as participants in the conflict or disagreement.
-
B.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
-
C.
disputeInvolves
Indicates that a particular dispute includes or concerns the specified entities as participants or parties to the conflict.
-
D.
partiesAre
Indicates that certain entities are the participants or sides involved in a particular relationship, agreement, or event.
-
E.
partOfWiderDispute
Indicates that one dispute is a component or subset of a larger, overarching dispute or conflict.
- 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_69e0b4c2b2a481909e31e9cb8f81ab55 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6c1917ce08190a54720d4d5b0a02c |
completed | April 21, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:13 p.m.