Triple
T5304188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Faultline |
E120055
|
entity |
| Predicate | matchdayLocation |
P63944
|
FINISHED |
| Object | supporters section at PayPal Park |
—
|
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 PayPal Park | Statement: [The Faultline, matchdayLocation, supporters section at PayPal Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchdayLocation Context triple: [The Faultline, matchdayLocation, supporters section at PayPal Park]
-
A.
locationOfCompetition
Indicates the place or venue where a competition or contest takes or took place.
-
B.
matchdayActivity
Indicates the specific activity, event, or engagement that takes place in connection with a particular match day.
-
C.
notableMatchVenueFor
Indicates that a venue is notably associated with hosting a particular match or game.
-
D.
matchOf
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
-
E.
locationTeam2Home
Indicates that the specified location serves as the home venue or home ground for the second team involved in the context.
- 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_69bd44704be88190acdb2ac481b0ff55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8e44e7c881909b241b2fec366038 |
completed | March 20, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69bd845097ac81909678624c4907fda4 |
completed | March 20, 2026, 5:30 p.m. |
| PDg | Predicate description generation | batch_69bd8e43c4c88190bb72b9bf56c99425 |
completed | March 20, 2026, 6:13 p.m. |
Created at: March 20, 2026, 1:53 p.m.