Triple
T24162462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cruzeiro Esporte Clube (majority stake) |
E598877
|
entity |
| Predicate | clubNotability |
P79581
|
FINISHED |
| Object | historic success in Brazilian football |
—
|
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: historic success in Brazilian football | Statement: [Cruzeiro Esporte Clube (majority stake), clubNotability, historic success in Brazilian football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clubNotability Context triple: [Cruzeiro Esporte Clube (majority stake), clubNotability, historic success in Brazilian football]
-
A.
sharesNotabilityWith
Indicates that two entities are notable or recognized for the same or closely related reason, characteristic, or achievement.
-
B.
notabilityScope
chosen
Indicates the domain, field, or context within which something is considered notable or significant.
-
C.
organNotability
Indicates that an organ is notable or significant in some specific context or for a particular purpose.
-
D.
coachNotability
Indicates that an individual is notable or distinguished specifically in their role as a coach.
-
E.
notabilityStatus
Indicates whether and how an entity is recognized as notable or significant within a given context or system.
- 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_69e288cb0a3081909ef221744f274384 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:32 p.m.