Triple
T29266843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campeonato Brasileiro Série D |
E741998
|
entity |
| Predicate | usesPointsSystemInGroups |
P177144
|
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: [Campeonato Brasileiro Série D, usesPointsSystemInGroups, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPointsSystemInGroups Context triple: [Campeonato Brasileiro Série D, usesPointsSystemInGroups, true]
-
A.
usesPointsSystem
Indicates that an entity operates or functions based on a structured points-based system for evaluation, rewards, or progression.
-
B.
usesGroup
Indicates that an entity makes use of, operates with, or relies on a particular group as a collective resource, tool, or participant in some activity or process.
-
C.
pointsSystemManagedBy
Indicates that the points system is overseen, controlled, or administered by a specified managing entity.
-
D.
usesPointsForLoss
Indicates that a system or rule assigns or deducts points to represent or account for a loss.
-
E.
hasBadgeSystem
Indicates that an entity includes or supports a badge-based system for recognizing or tracking achievements, statuses, or milestones.
- 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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6f85bfba48190aba95b40642a8ca7 |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f854486c81909396d944a55e03ab |
completed | May 3, 2026, 7:25 a.m. |
Created at: April 28, 2026, 12:45 p.m.