Triple
T5248866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assyriska FF |
E118530
|
entity |
| Predicate | notableCupPerformance |
P36409
|
FINISHED |
| Object | Svenska Cupen finalist 2003 |
—
|
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: Svenska Cupen finalist 2003 | Statement: [Assyriska FF, notableCupPerformance, Svenska Cupen finalist 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCupPerformance Context triple: [Assyriska FF, notableCupPerformance, Svenska Cupen finalist 2003]
-
A.
hasNotablePerformanceIn
Indicates that an entity delivered a significant or distinguished performance within a specified work, event, or context.
-
B.
notableWin
Indicates that one entity achieved a particularly significant or distinguished victory over another or in a specific event.
-
C.
notableOutcome
Indicates that an action, event, or entity leads to or is associated with a significant, noteworthy result or consequence.
-
D.
notablePlayerAchievement
Indicates that a player has accomplished a particularly significant or distinguished achievement within their activity or domain.
-
E.
hasNotablePerformance
chosen
Indicates that an entity has delivered a performance that is distinguished, remarkable, or otherwise noteworthy in a particular 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_69bd4468aacc8190a8196f71855cdf4f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b787b34819081af96de9355bb4f |
completed | March 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69bd77c30bac8190a883ca45da35d667 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:50 p.m.