Triple
T5870292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Major League Soccer All-Star Game |
E130498
|
entity |
| Predicate | typicalOpponent |
P54987
|
FINISHED |
| Object | international club team |
—
|
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: international club team | Statement: [Major League Soccer All-Star Game, typicalOpponent, international club team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalOpponent Context triple: [Major League Soccer All-Star Game, typicalOpponent, international club team]
-
A.
rivalOf
Indicates a relationship in which two entities compete against or oppose each other, often seeking advantage in the same domain or objective.
-
B.
battleOpponent
Indicates that two entities are engaged in or designated as opponents in a battle or combat scenario.
-
C.
featuresOpponentType
chosen
Indicates that an entity involves, includes, or is associated with an opponent of a specified type within a competitive or adversarial context.
-
D.
opponentStrength
Indicates the level or degree of power, skill, or capability possessed by an opposing party in a competitive or adversarial context.
-
E.
keyOpponents
Indicates that the subject has primary or most significant opponents identified by the object.
- 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_69c0085047dc8190af24e311edad3c07 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ffaef081909faaa7f420a3b9b7 |
completed | March 22, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69c03347e51c81909053bcf34e3b88ab |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:56 p.m.