Triple
T23900347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Os Três Grandes |
E601023
|
entity |
| Predicate | dominatesCompetition |
P6615
|
FINISHED |
| Object | Portuguese league titles |
—
|
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: Portuguese league titles | Statement: [Os Três Grandes, dominatesCompetition, Portuguese league titles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominatesCompetition Context triple: [Os Três Grandes, dominatesCompetition, Portuguese league titles]
-
A.
competesWith
Indicates that two entities are in rivalry or opposition, each striving to outperform or gain advantage over the other in the same domain or objective.
-
B.
primaryCompetition
chosen
Indicates that one entity is the main or most significant competitor of another within a given market, domain, or context.
-
C.
tieneCompetenciaEn
Indicates that an entity possesses skill, expertise, or competence in a specific area, field, or activity.
-
D.
isCompetitive
Indicates that one entity engages in rivalry or competition with another, typically striving to outperform or win against it.
-
E.
tieneCompetencia
Indicates that one entity has or faces competition from another entity.
- 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_69e295364a488190bcac702e9bb7f764 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cdddca088190b6c26df984a143ad |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:26 p.m.