Triple
T25906024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Privateers 1882 |
E652752
|
entity |
| Predicate | supportsHomeStadium |
P890
|
FINISHED |
| Object | Wanderers Grounds |
—
|
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: Wanderers Grounds | Statement: [Privateers 1882, supportsHomeStadium, Wanderers Grounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsHomeStadium Context triple: [Privateers 1882, supportsHomeStadium, Wanderers Grounds]
-
A.
supportsHomeMatchesOf
Indicates that one entity provides backing, resources, or assistance specifically for the home matches of another entity.
-
B.
isLocalStadiumFor
Indicates that a stadium serves as the primary home venue for a particular local team, club, or community.
-
C.
hasHomeStadiumContext
Indicates that an entity’s home stadium is specified or characterized within a particular contextual framework (such as time, competition, or role).
-
D.
homeStadium
chosen
Indicates that a particular stadium serves as the primary venue where a sports team plays its home games.
-
E.
homeStadiumFeatureOf
Indicates that a stadium serves as the designated home venue or primary hosting facility for a particular team, club, or organization.
- 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_69e7ab3d3f8481909bc53ed64c06af33 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: April 22, 2026, 8:27 a.m.