Triple
T32170310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2021 British & Irish Lions tour to South Africa |
E821691
|
entity |
| Predicate | testVenueCity |
P19642
|
FINISHED |
| Object | Cape Town |
—
|
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: Cape Town | Statement: [2021 British & Irish Lions tour to South Africa, testVenueCity, Cape Town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testVenueCity Context triple: [2021 British & Irish Lions tour to South Africa, testVenueCity, Cape Town]
-
A.
cityOfVenue
chosen
Indicates the city in which a given venue is located.
-
B.
typicalVenueCity
Indicates that a particular city is the usual or standard location where an event, activity, or organization is typically held or based.
-
C.
hasListingVenueCity
Indicates that an entity’s listing is associated with a specific city as its venue location.
-
D.
hasVenueName
Indicates that an entity has a specific name used to identify the venue where an event or activity takes place.
-
E.
operatesVenueInCity
Indicates that an entity operates or manages a venue located within a specified city.
- 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_69f3490699a48190bbef96b198e8fade |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ba73aa9c819082328ddf6ec799ec |
completed | May 3, 2026, 3:01 a.m. |
| PD | Predicate disambiguation | batch_69f6b3aa892481908d29283a074e6722 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:33 a.m.