Triple
T27838968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montenegrin Cup |
E703625
|
entity |
| Predicate | domesticCupHierarchy |
P165416
|
FINISHED |
| Object | primary national cup of Montenegro |
—
|
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: primary national cup of Montenegro | Statement: [Montenegrin Cup, domesticCupHierarchy, primary national cup of Montenegro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domesticCupHierarchy Context triple: [Montenegrin Cup, domesticCupHierarchy, primary national cup of Montenegro]
-
A.
domesticCup
Indicates that an entity has won or participated in a domestic (national-level) cup competition within its sport or domain.
-
B.
domesticCupHierarchyPosition
Indicates the relative ranking or level of a team or participant within the structure or tiers of a domestic cup competition.
-
C.
domesticCupLevel
Indicates the competitive tier or stage of a team’s participation within a domestic cup competition.
-
D.
domesticCupReputation
Indicates the level of recognition or prestige an entity has earned through performance in domestic cup competitions.
-
E.
numberOfCups
Indicates the quantity of cups associated with a given entity or context.
- F. None of above. chosen
Provenance (4 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_69ef840d9e3c819093615ebff4ec22be |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f659355a208190be2609ffc7a9c427 |
completed | May 2, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f65875030881909007c502b7dcc998 |
completed | May 2, 2026, 8:03 p.m. |
Created at: April 27, 2026, 6:01 p.m.