Triple
T35477200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super League Grand Final |
E1025367
|
entity |
| Predicate | cityOfTypicalVenue |
P15624
|
FINISHED |
| Object | Manchester |
—
|
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: Manchester | Statement: [Super League Grand Final, cityOfTypicalVenue, Manchester]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityOfTypicalVenue Context triple: [Super League Grand Final, cityOfTypicalVenue, Manchester]
-
A.
typicalVenueCity
chosen
Indicates that a particular city is the usual or standard location where an event, activity, or organization is typically held or based.
-
B.
typicalVenueMetroArea
Indicates the metropolitan area where an entity is most commonly or characteristically located or hosted.
-
C.
typicalVenues
Indicates that the specified locations are common or standard places where the associated activity, event, or entity usually occurs or is hosted.
-
D.
cityOfVenue
Indicates the city in which a given venue is located.
-
E.
formerTypicalVenue
Indicates that a location was once the usual or primary venue for an entity’s activities or events, but no longer serves in that typical role.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:04 p.m.