Triple
T25168753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portuguese League Cup |
E630255
|
entity |
| Predicate | hasBigThreeDominance |
P107936
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Portuguese League Cup, hasBigThreeDominance, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBigThreeDominance Context triple: [Portuguese League Cup, hasBigThreeDominance, yes]
-
A.
bigThreeWith
Indicates a relationship where three entities are grouped or associated together as a primary or most significant trio in a given context.
-
B.
championshipDominatedBy
chosen
Indicates that a particular championship is overwhelmingly controlled or won by a specific entity (such as a team, player, or organization) over a period of time.
-
C.
hasLongServingPlayer
Indicates that an entity is associated with a player who has been serving or active for a long duration.
-
D.
hasDominion
Indicates that one entity holds authority, control, or governing power over another entity or domain.
-
E.
hasMajorFranchise
Indicates that an entity possesses or is associated with a primary, large-scale franchise within a broader domain or organization.
- 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_69e75a87c9b88190ab60731902a99750 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 12:18 p.m.