Triple
T22271427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atléticos de San Germán |
E550485
|
entity |
| Predicate | homeCompetitionLevel |
P18266
|
FINISHED |
| Object | first division |
—
|
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: first division | Statement: [Atléticos de San Germán, homeCompetitionLevel, first division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeCompetitionLevel Context triple: [Atléticos de San Germán, homeCompetitionLevel, first division]
-
A.
primaryCompetitionLevel
chosen
Indicates the main or highest level of competition at which an entity primarily competes or operates.
-
B.
featuredCompetitionLevel
Indicates that a particular competition level is highlighted or given special prominence relative to other levels.
-
C.
homeTournament
Indicates that a tournament is being held at or hosted by the referenced entity’s home venue or location.
-
D.
competitionLevelOf
Indicates the degree or intensity of competitiveness associated with an entity, event, or context.
-
E.
competitionLevel
Indicates the degree or intensity of competitive pressure or rivalry present in a given context or interaction.
- 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_69e11e43d8208190aff4f9cf7f2c2a8a |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f141c056cc819088dae6f2b9a1d526 |
completed | April 28, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:40 p.m.