Triple
T31034929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calcutta Cup |
E790827
|
entity |
| Predicate | hasAssociatedNation |
P33828
|
FINISHED |
| Object | United Kingdom |
—
|
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: United Kingdom | Statement: [Calcutta Cup, hasAssociatedNation, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedNation Context triple: [Calcutta Cup, hasAssociatedNation, United Kingdom]
-
A.
belongsToNationState
Indicates that an entity is a member, part, or constituent of a specific nation-state, reflecting a formal or recognized association with that country.
-
B.
associatedWithNationality
chosen
Indicates that one entity has a connection or affiliation with the nationality of another entity.
-
C.
hasPrimaryNation
Indicates that one entity is designated as the main or principal nation associated with another entity.
-
D.
hasTerritorialAssociation
Indicates a relationship where an entity is linked or connected to a specific territory, area, or geographic region.
-
E.
hasCountry
Indicates that one entity possesses, is associated with, or is located within a specific country.
- 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_69f224c97a788190b5da1ead6038a74e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 29, 2026, 8:59 p.m.