Triple
T2987712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tower Bridge Battalion |
E80666
|
entity |
| Predicate | typicalLocationDuringMatches |
P12966
|
FINISHED |
| Object | behind the goal at Sacramento Republic FC home stadium |
—
|
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: behind the goal at Sacramento Republic FC home stadium | Statement: [Tower Bridge Battalion, typicalLocationDuringMatches, behind the goal at Sacramento Republic FC home stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLocationDuringMatches Context triple: [Tower Bridge Battalion, typicalLocationDuringMatches, behind the goal at Sacramento Republic FC home stadium]
-
A.
typicalGameLocation
chosen
Indicates the usual or characteristic place where a game is played or takes place.
-
B.
locationOfCompetition
Indicates the place or venue where a competition or contest takes or took place.
-
C.
arenaLocation
Indicates that an arena is located at or within a specified place or geographic location.
-
D.
notableMatchVenueFor
Indicates that a venue is notably associated with hosting a particular match or game.
-
E.
trainingCampLocation
Indicates the place where a training camp is held or based.
- 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_69ad8b16c3488190b47b6aa7a59a335b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99c88f608190bf734e0b744bf3d1 |
completed | March 8, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ad961403108190bbecb8d3608fd4e0 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.