Triple
T13935894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States men’s national rugby union team |
E335119
|
entity |
| Predicate | traditionalRegionRival |
P80695
|
FINISHED |
| Object | Americas teams |
—
|
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: Americas teams | Statement: [United States men’s national rugby union team, traditionalRegionRival, Americas teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalRegionRival Context triple: [United States men’s national rugby union team, traditionalRegionRival, Americas teams]
-
A.
rivalryRegion
chosen
Indicates a competitive or adversarial relationship that exists between entities within a specific geographic or regional context.
-
B.
associatedRivalry
Indicates a relationship where one entity is linked to another as its rival, competitor, or opposing counterpart.
-
C.
hasLocalRivalry
Indicates that there is an ongoing competitive or adversarial relationship between entities that are geographically close or share the same local area.
-
D.
rivalryInvolvesCity
Indicates that a rivalry relationship includes or is associated with a particular city as one of its involved locations.
-
E.
isPartOfRivalry
Indicates that one entity participates as a member or component in an ongoing rivalry involving another entity.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2cf42878819085146670d7b92605 |
completed | April 14, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69dbc873052c8190b33ff7f7c5a4e7ee |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:17 p.m.