Triple
T24568402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EuroCup Women |
E607859
|
entity |
| Predicate | tierInEurope |
P148427
|
FINISHED |
| Object | second tier |
—
|
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: second tier | Statement: [EuroCup Women, tierInEurope, second tier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tierInEurope Context triple: [EuroCup Women, tierInEurope, second tier]
-
A.
tierInRegion
chosen
Indicates that an entity is assigned to a specific tier or level within a given region or geographic area.
-
B.
tierInBelgium
Indicates that an entity belongs to, is classified within, or operates at a specific tier or level in the context of Belgium.
-
C.
tierInNorthAmericanSystem
Indicates that an entity occupies a specified competitive or organizational level within the North American system for that domain (e.g., sports leagues, education, or other structured hierarchies).
-
D.
tierInDomesticSystem
Indicates the hierarchical level or rank that an entity occupies within a country's internal (domestic) system or structure.
-
E.
tierType
Indicates the classification level or rank assigned to an entity within a multi-level or hierarchical 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_69e2c4cc35a48190990b7571bc086df8 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9225d9c8190ae92e5540f6c45c2 |
completed | April 30, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:28 a.m.