Triple
T18445652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barron Report |
E450648
|
entity |
| Predicate | inquiryScope |
P87971
|
FINISHED |
| Object | events of 17 May 1974 in Dublin and Monaghan |
—
|
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: events of 17 May 1974 in Dublin and Monaghan | Statement: [Barron Report, inquiryScope, events of 17 May 1974 in Dublin and Monaghan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inquiryScope Context triple: [Barron Report, inquiryScope, events of 17 May 1974 in Dublin and Monaghan]
-
A.
acquisitionScope
Indicates the extent, boundaries, or coverage of what is obtained or brought under control through an acquisition.
-
B.
inquiry
Indicates that one entity seeks information, clarification, or an answer from another through a question or request.
-
C.
scopeOfProducts
Indicates the range or extent of products that fall under a particular category, responsibility, or context.
-
D.
investigativeScope
chosen
Indicates the range or extent of subjects, issues, or activities that an investigation is intended to examine or cover.
-
E.
scopeOfSales
Indicates the range, extent, or boundaries within which sales activities, rights, or transactions are valid or permitted.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51c15127881909d23b6dd45d7ccc9 |
completed | April 19, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:30 a.m.