Triple
T29102395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Hoops |
E736670
|
entity |
| Predicate | usedInMatchReportsToReferTo |
P42513
|
FINISHED |
| Object | Shamrock Rovers F.C. |
—
|
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: Shamrock Rovers F.C. | Statement: [The Hoops, usedInMatchReportsToReferTo, Shamrock Rovers F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInMatchReportsToReferTo Context triple: [The Hoops, usedInMatchReportsToReferTo, Shamrock Rovers F.C.]
-
A.
usedInMatch
Indicates that something (such as an item, tactic, or resource) was employed or utilized during a particular match or game.
-
B.
usedInOfficialMatchReports
chosen
Indicates that something is included or referenced within formal, authoritative match reports.
-
C.
usedInMatchSchedules
Indicates that something (such as a resource, rule, or configuration) is utilized within the scheduling or arrangement of matches.
-
D.
usedInMatchType
Indicates that something (such as a rule, item, or configuration) is applied or relevant within a specific type or category of match.
-
E.
usedInFriendlyMatches
Indicates that something (such as a rule, tactic, or item) is employed or applied specifically in the context of friendly (non-competitive) matches.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: April 28, 2026, 11:13 a.m.