Triple
T29901551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reading FC |
E759418
|
entity |
| Predicate | formerTrainingGround |
P34366
|
FINISHED |
| Object | Hogwood Park |
—
|
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: Hogwood Park | Statement: [Reading FC, formerTrainingGround, Hogwood Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerTrainingGround Context triple: [Reading FC, formerTrainingGround, Hogwood Park]
-
A.
trainingGroundFor
Indicates that one entity serves as a place or context where another entity is trained, prepared, or developed.
-
B.
trainingGround
Indicates a location or context where entities engage in practice, drills, or preparation activities to develop or improve skills.
-
C.
formerGround
chosen
Indicates that an entity previously served as the ground or base for another entity but no longer holds that role.
-
D.
previousTrainingLocation
Indicates the place where an entity received training immediately before the current or referenced training event.
-
E.
providesTrainingFor
Indicates that one entity delivers or conducts training activities intended to develop the skills or knowledge of another entity.
- 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_69f224600590819085e148a01c056ef6 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69feb342994081909481ec8ec5d44928 |
completed | May 9, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69feb046e4e48190b96649aa28529cc9 |
completed | May 9, 2026, 3:55 a.m. |
Created at: April 29, 2026, 6:06 p.m.