Triple
T29031278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goodman Stadium |
E737732
|
entity |
| Predicate | previousHomeVenueOf |
P56486
|
FINISHED |
| Object | Philadelphia Eagles training camp |
—
|
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: Philadelphia Eagles training camp | Statement: [Goodman Stadium, previousHomeVenueOf, Philadelphia Eagles training camp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousHomeVenueOf Context triple: [Goodman Stadium, previousHomeVenueOf, Philadelphia Eagles training camp]
-
A.
formerHomeVenue
chosen
Indicates that a location previously served as the primary venue or home ground for an entity, but no longer holds that status.
-
B.
previousVenue
Indicates that one venue was used or occupied before another in a sequence of venues.
-
C.
previousHomeVenueForTeam
Indicates that a venue formerly served as the home venue for a given team, but no longer does so.
-
D.
previousHomeGroundLocatedIn
Indicates that the location specified is where an entity’s former or earlier home ground was situated.
-
E.
homeVenueOfOwnedTeam
Indicates that a venue serves as the primary home location for a sports team that is owned by a specified owner.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
Created at: April 28, 2026, 9:55 a.m.