Triple
T25972487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radio London |
E645842
|
entity |
| Predicate | regulatoryConflictWith |
P4897
|
FINISHED |
| Object | British government |
—
|
NE NERFINISHED |
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: British government | Statement: [Radio London, regulatoryConflictWith, British government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatoryConflictWith Context triple: [Radio London, regulatoryConflictWith, British government]
-
A.
conflictWithLaw
Indicates that an action, situation, or entity violates, contradicts, or is incompatible with a law or legal regulation.
-
B.
conflictWith
chosen
Indicates that two entities are in opposition or disagreement, such that their goals, actions, or states are incompatible or interfere with each other.
-
C.
jurisdictionConflictWith
Indicates a situation where the legal or authoritative jurisdiction of one entity overlaps with, challenges, or is incompatible with that of another entity.
-
D.
reportedConflict
Indicates that one party has formally reported the existence of a conflict involving another party or situation.
-
E.
mentionsConflict
Indicates that one entity refers to or discusses a dispute, disagreement, or conflict involving 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_69e77e8768648190b27bb578f14bcb88 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 22, 2026, 8:51 a.m.