Triple
T9781982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Commission on Local Government in Greater London |
E237396
|
entity |
| Predicate | reportPublished |
P35063
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [Royal Commission on Local Government in Greater London, reportPublished, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportPublished Context triple: [Royal Commission on Local Government in Greater London, reportPublished, 1960s]
-
A.
reportPublishedIn
Indicates that a specific report appears as content within, or is formally issued through, a particular publication venue (such as a journal, magazine, or report series).
-
B.
reportsPublication
Indicates that an entity (such as an author, organization, or system) formally issues or announces a specific publication.
-
C.
reportPublisher
chosen
Indicates that one entity is the organization or individual responsible for publishing a given report.
-
D.
publishedNewspaper
Indicates that an entity produced and issued a newspaper for public distribution.
-
E.
report
Indicates that one entity formally provides information or an account about another entity, event, or situation, typically for documentation, communication, or evaluation purposes.
- 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_69ca84da927881909bda80caecad6010 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda1b23cb88190b458ab18d5f7f493 |
completed | April 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69cd03d77c6c81909b675955bf113320 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:27 p.m.