Triple
T27378895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vitória S.C. |
E691158
|
entity |
| Predicate | regularCompetitionLevel |
P18266
|
FINISHED |
| Object | top division of Portuguese 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: top division of Portuguese football | Statement: [Vitória S.C., regularCompetitionLevel, top division of Portuguese football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regularCompetitionLevel Context triple: [Vitória S.C., regularCompetitionLevel, top division of Portuguese football]
-
A.
levelOfCompetitionAdministered
Indicates the specific competitive tier or intensity at which an activity, event, or process is formally managed or overseen.
-
B.
competitionLevel
Indicates the degree or intensity of competitive pressure or rivalry present in a given context or interaction.
-
C.
competitionLevelOf
Indicates the degree or intensity of competitiveness associated with an entity, event, or context.
-
D.
levelOfCompetition
Indicates the intensity or degree of competitive pressure present in a given context or interaction.
-
E.
primaryCompetitionLevel
chosen
Indicates the main or highest level of competition at which an entity primarily competes or operates.
- 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_69ef52022538819081f873d0c84a6dd6 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 27, 2026, 12:22 p.m.