Triple
T29773146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Anglian derby |
E755301
|
entity |
| Predicate | homeGroundOfNorwichCity |
P164581
|
FINISHED |
| Object | Carrow Road |
—
|
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: Carrow Road | Statement: [East Anglian derby, homeGroundOfNorwichCity, Carrow Road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeGroundOfNorwichCity Context triple: [East Anglian derby, homeGroundOfNorwichCity, Carrow Road]
-
A.
homeGroundOfDerbyCounty
Indicates that a location serves as the home ground (primary home stadium or venue) for the Derby County team.
-
B.
homeGroundOfAssociatedClub
chosen
Indicates that a particular venue or ground serves as the designated home location for an associated sports club.
-
C.
homeGroundTown
Indicates that a particular town is recognized as the home ground or primary hosting location for a team, organization, or entity.
-
D.
hasHomeGroundForSunderland
Indicates that a location serves as the home ground (primary home venue) for the Sunderland team.
-
E.
homeStadiumNorthernIreland
Indicates that a stadium serves as the designated home venue for a team or organization associated with Northern Ireland.
- 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_69f0ef878574819088c867fd1a5c8b86 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f67463b0d48190ba31b4c1d78da062 |
completed | May 2, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 8:44 p.m.