Triple
T25942652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boavista F.C. |
E653747
|
entity |
| Predicate | isRareChampionOutsideBigThree |
P159584
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Boavista F.C., isRareChampionOutsideBigThree, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRareChampionOutsideBigThree Context triple: [Boavista F.C., isRareChampionOutsideBigThree, true]
-
A.
notableMultipleIndividualChampion
Indicates that an entity has achieved champion status multiple times, highlighting repeated notable victories or titles.
-
B.
championRank
Indicates the relative level or position of an entity within a competitive ranking or championship hierarchy.
-
C.
firstChampion
Indicates that one entity is the earliest or original champion or title-holder in relation to another entity.
-
D.
isRelativelyRareName
Indicates that the referenced name occurs infrequently relative to other names in the relevant population or dataset.
-
E.
featuredChampion
Indicates that an entity is highlighted or designated as a primary or special champion in a given context or event.
- 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_69e7ab3fd2f881908837305e4ba98011 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6045ec5708190917d60774389e68c |
completed | May 2, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 22, 2026, 8:41 a.m.