Triple
T25906033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Privateers 1882 |
E652752
|
entity |
| Predicate | homeEndLocation |
P159558
|
FINISHED |
| Object | supporters section at Wanderers Grounds |
—
|
LITERAL FINISHED |
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: supporters section at Wanderers Grounds | Statement: [Privateers 1882, homeEndLocation, supporters section at Wanderers Grounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeEndLocation Context triple: [Privateers 1882, homeEndLocation, supporters section at Wanderers Grounds]
-
A.
homeTo
Indicates that a place serves as the primary location, residence, or habitat for a person, group, or thing.
-
B.
homeBaseOf
Indicates that a particular place serves as the primary location, headquarters, or main operational base for an entity.
-
C.
homeEndInStadium
Indicates that a team's home games are played in a particular stadium.
-
D.
isHomeEndFor
Indicates that something serves as the final destination, endpoint, or concluding location for a journey, process, or sequence.
-
E.
endLocationOfJourney
Indicates the final destination or stopping point reached at the conclusion of a journey or trip.
- F. None of above. chosen
Provenance (4 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_69f603beb5248190aed52bf4e44f223c |
completed | May 2, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 22, 2026, 8:27 a.m.