Triple
T13799615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frölunda–Färjestad rivalry |
E331603
|
entity |
| Predicate | typicalMatchContext |
P35407
|
FINISHED |
| Object | league games |
—
|
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: league games | Statement: [Frölunda–Färjestad rivalry, typicalMatchContext, league games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMatchContext Context triple: [Frölunda–Färjestad rivalry, typicalMatchContext, league games]
-
A.
typicalMatchType
Indicates the usual or most common type of match or pairing that characterizes how two entities are related or aligned.
-
B.
matchContext
chosen
Indicates that two or more entities are related within the same situational, conversational, or environmental setting that frames or influences their interaction.
-
C.
typicalMatchRules
Indicates that two entities are considered a standard or default match according to predefined matching rules or criteria.
-
D.
typicalAppearanceContext
Indicates the usual situation, setting, or context in which an entity most commonly appears or is typically encountered.
-
E.
hasTypicalUseContext
Indicates that something is commonly or characteristically used within a particular situation, setting, or context.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de025ce9148190b23370f6a522ff7a |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:11 p.m.