Triple
T614017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FA Community Shield |
E12162
|
entity |
| Predicate | usualVenueSince |
P17127
|
FINISHED |
| Object | 1974 |
—
|
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: 1974 | Statement: [FA Community Shield, usualVenueSince, 1974]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usualVenueSince Context triple: [FA Community Shield, usualVenueSince, 1974]
-
A.
primaryVenueFor
Indicates that one entity serves as the main or principal venue or location for events, activities, or operations associated with another entity.
-
B.
previousVenue
Indicates that one venue was used or occupied before another in a sequence of venues.
-
C.
venue
Indicates the place or location where an event, activity, or interaction takes place.
-
D.
primaryVenues
Indicates the main or most important venues associated with or used by a given entity.
-
E.
legacyVenue
Indicates that a venue has historical or long-standing significance, often preserved or recognized due to its past importance or enduring role.
- 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_69a493309df48190a327f748e88049a6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49e0a0f588190b953fdb585263307 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfbcbf88190a854921dc531eba8 |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49def31ec81909dc53e70f4a36eda |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:35 p.m.