Triple
T30645497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Law Reports (England and Wales) |
E780107
|
entity |
| Predicate | publishesFrom |
P50067
|
FINISHED |
| Object | courts of England and Wales |
—
|
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: courts of England and Wales | Statement: [Law Reports (England and Wales), publishesFrom, courts of England and Wales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publishesFrom Context triple: [Law Reports (England and Wales), publishesFrom, courts of England and Wales]
-
A.
publishesTo
Indicates that one entity distributes, releases, or makes content available to another entity or destination.
-
B.
publishesFor
Indicates that one entity issues, releases, or makes content publicly available on behalf of, or in service of, another entity.
-
C.
publishesAuthorsFrom
Indicates that a publisher releases works created by the specified authors.
-
D.
publishesWorkFrom
chosen
Indicates that an entity (such as a publisher or platform) issues or makes public a work that originates from a particular source entity.
-
E.
publishedTo
Indicates that something has been made publicly available or distributed to an audience, platform, or destination.
- 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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
Created at: April 29, 2026, 8:29 p.m.