Triple
T36717590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barbarian F.C. |
E906955
|
entity |
| Predicate | famousMatchFeature |
P186236
|
FINISHED |
| Object | Gareth Edwards’ try in 1973 vs New Zealand |
—
|
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’ try in 1973 vs New Zealand | Statement: [Barbarian F.C., famousMatchFeature, Gareth Edwards’ try in 1973 vs New Zealand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousMatchFeature Context triple: [Barbarian F.C., famousMatchFeature, Gareth Edwards’ try in 1973 vs New Zealand]
-
A.
famousMatch
Indicates that two entities are linked by a match or pairing that is widely known or celebrated.
-
B.
featuresMatchType
Indicates that the features involved conform to, or are compatible with, a specified type or classification.
-
C.
famousPattern
Indicates that one entity is widely recognized or renowned for a particular style, design, or recurring configuration associated with it.
-
D.
sharesFeatureExtractor
Indicates that two or more models or components use the same feature extraction mechanism or module.
-
E.
featuredMatchType
Indicates the specific category or kind of match that is highlighted or given special prominence.
- F. None of above. chosen
Provenance (4 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_69f76e73ad108190a5241585f2303e9a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7cabacc1481909e839454ce1057f7 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7c9f4c7c48190ba918d8d5dc8dfd9 |
completed | May 3, 2026, 10:19 p.m. |
Created at: May 3, 2026, 4:12 p.m.