Triple
T22622692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eerste Divisie |
E558325
|
entity |
| Predicate | reserveTeamsFrom |
P71524
|
FINISHED |
| Object | Eredivisie clubs |
—
|
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: Eredivisie clubs | Statement: [Eerste Divisie, reserveTeamsFrom, Eredivisie clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reserveTeamsFrom Context triple: [Eerste Divisie, reserveTeamsFrom, Eredivisie clubs]
-
A.
hasReserveTeam
Indicates that an organization, typically a sports club, maintains a secondary or backup team formally associated with its main team.
-
B.
eligibleTeamsFrom
Indicates that certain teams qualify or are allowed to originate from a specified source, context, or selection criteria.
-
C.
reserveTeamRules
Indicates that there are specific rules or regulations governing the use, composition, or operation of a reserve team.
-
D.
reserveTeamsCannotPlayInSameDivisionAsFirstTeam
Indicates that reserve teams are not allowed to compete in the same division as their associated first (main) team.
-
E.
allowsReserveTeamsInPyramid
chosen
Indicates that the competition structure permits reserve teams to participate within the main league pyramid 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_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.