Triple
T26795270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kidderminster Carolians RFC |
E670927
|
entity |
| Predicate | hasHomeMatchesLocation |
P8186
|
FINISHED |
| Object | Kidderminster |
—
|
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: Kidderminster | Statement: [Kidderminster Carolians RFC, hasHomeMatchesLocation, Kidderminster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeMatchesLocation Context triple: [Kidderminster Carolians RFC, hasHomeMatchesLocation, Kidderminster]
-
A.
hostedHomeMatchesFor
Indicates that an entity organized and held competitive matches at its own home venue for another entity or group.
-
B.
supportsHomeMatchesOf
Indicates that one entity provides backing, resources, or assistance specifically for the home matches of another entity.
-
C.
hasHomeCity
Indicates that an entity’s primary or official city of residence or affiliation is a specified city.
-
D.
playedHomeMatchesIn
chosen
Indicates that an entity (typically a sports team) hosted its home matches at a specified venue or location.
-
E.
hasHomeDerbyFor
Indicates that one entity serves as the home venue or location where another entity’s derby event is held.
- 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_69eeb31fbd888190a82dac5822e453bc |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 27, 2026, 4:19 a.m.