Triple
T32305113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RSEA Park |
E825341
|
entity |
| Predicate | trainingBaseOf |
P42544
|
FINISHED |
| Object | St Kilda Football Club |
—
|
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: St Kilda Football Club | Statement: [RSEA Park, trainingBaseOf, St Kilda Football Club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trainingBaseOf Context triple: [RSEA Park, trainingBaseOf, St Kilda Football Club]
-
A.
trainingBase
Indicates that one entity serves as the training base, site, or facility where another entity receives training or instruction.
-
B.
trainingBaseRegion
Indicates the geographic region where an entity’s training activities or training base is located or conducted.
-
C.
trainingGround
Indicates a location or context where entities engage in practice, drills, or preparation activities to develop or improve skills.
-
D.
hasTrainingBaseIn
Indicates that an entity maintains or operates a training base located in a specified place.
-
E.
trainingGroundFor
chosen
Indicates that one entity serves as a place or context where another entity is trained, prepared, or developed.
- 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_69f349115304819084ee91d345b6c8aa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 12:45 a.m.