Triple
T11151627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barbarians |
E263799
|
entity |
| Predicate | notableMatchFeature |
P9490
|
FINISHED |
| Object | Gareth Edwards’ famous try vs New Zealand in 1973 |
—
|
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: Gareth Edwards’ famous try vs New Zealand in 1973 | Statement: [Barbarians, notableMatchFeature, Gareth Edwards’ famous try vs New Zealand in 1973]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMatchFeature Context triple: [Barbarians, notableMatchFeature, Gareth Edwards’ famous try vs New Zealand in 1973]
-
A.
notableMatch
Indicates that there exists a particularly significant or noteworthy match or pairing between the related entities.
-
B.
notableMatchVenueFor
Indicates that a venue is notably associated with hosting a particular match or game.
-
C.
notablePlay
chosen
Indicates that a particular play is especially famous, significant, or noteworthy in relation to the entity it is associated with.
-
D.
notableLeagueCharacteristic
Indicates that a particular characteristic is especially prominent or defining for a given league.
-
E.
featuredMatchType
Indicates the specific category or kind of match that is highlighted or given special prominence.
- 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8719e74819095413abc6c79296c |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75ce71944819089eee9b5c9283cbd |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:28 p.m.