Triple
T35517472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arsenal Stadium, Highbury |
E1026456
|
entity |
| Predicate | servedAsHomeGroundFor |
P195800
|
FINISHED |
| Object | Arsenal F.C. |
—
|
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: Arsenal F.C. | Statement: [Arsenal Stadium, Highbury, servedAsHomeGroundFor, Arsenal F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedAsHomeGroundFor Context triple: [Arsenal Stadium, Highbury, servedAsHomeGroundFor, Arsenal F.C.]
-
A.
playedAtStadium
Indicates that an event or game took place at, or was hosted in, a specific stadium.
-
B.
playedHomeGamesOn
chosen
Indicates that a team or player held their home games at a particular venue or location.
-
C.
playedHomeMatchesIn
Indicates that an entity (typically a sports team) hosted its home matches at a specified venue or location.
-
D.
hasLocalRivalryVenueWith
Indicates that two entities share a venue or location where a local rivalry between them is regularly contested or expressed.
-
E.
previousHomeGroundLocatedIn
Indicates that the location specified is where an entity’s former or earlier home ground was situated.
- 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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00144238708190acbec3f791cc873e |
completed | May 10, 2026, 5:14 a.m. |
| PD | Predicate disambiguation | batch_6a00120244a4819090ef39070aba9d99 |
completed | May 10, 2026, 5:05 a.m. |
Created at: May 3, 2026, 4:04 p.m.