Triple
T22622668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eerste Divisie |
E558325
|
entity |
| Predicate | positionInDutchLeagueSystem |
P41168
|
FINISHED |
| Object | below Eredivisie |
—
|
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: below Eredivisie | Statement: [Eerste Divisie, positionInDutchLeagueSystem, below Eredivisie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInDutchLeagueSystem Context triple: [Eerste Divisie, positionInDutchLeagueSystem, below Eredivisie]
-
A.
positionInLeagueSystem
chosen
Indicates the rank or tier an entity holds within an organized league or competitive system.
-
B.
countryLeagueSystem
Indicates that a particular league system operates within, or is associated with, a specific country.
-
C.
rankAmongEuropeanLeagues
Indicates the position or standing of something relative to other entities within the set of European leagues.
-
D.
levelInUEFASystem
Indicates the specific tier or division an entity occupies within the hierarchical structure of the UEFA football league system.
-
E.
countryLeagueRepresents
Indicates that a particular league serves as the official representative or embodiment of a country in a given sport or competitive context.
- 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_69e24545a8e08190bfa7482a2c725ff1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f16e3ad6f48190b351a52e4b1d9b2d |
completed | April 29, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 3 p.m.