Triple
T25983224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Local Government Official Information and Meetings Act 1987 |
E646125
|
entity |
| Predicate | citationContainsYear |
P25
|
FINISHED |
| Object | 1987 |
—
|
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: 1987 | Statement: [Local Government Official Information and Meetings Act 1987, citationContainsYear, 1987]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: citationContainsYear Context triple: [Local Government Official Information and Meetings Act 1987, citationContainsYear, 1987]
-
A.
relatedWorkPublicationYear
Indicates the year in which a related work associated with the primary entity was published.
-
B.
appearsInPublicationYear
Indicates that an entity is featured in a publication that was released in a specific year.
-
C.
collectedInPublicationYear
Indicates that the collecting event or data record was documented in a publication that appeared in the specified year.
-
D.
publicationYear
chosen
Indicates the specific calendar year in which a work was formally published or released.
-
E.
authorWorkPublicationYear
Indicates the year in which a specific work created by an author was published.
- 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_69e77e881fc08190ba1c8dc7e2a07f97 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f60511cfe88190b2b88b40fb4ec269 |
completed | May 2, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:54 a.m.