Triple
T15118004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fairs Cup Committee |
E361091
|
entity |
| Predicate | basedOnCompetitionType |
P99812
|
FINISHED |
| Object | trade fairs cities concept |
—
|
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: trade fairs cities concept | Statement: [Fairs Cup Committee, basedOnCompetitionType, trade fairs cities concept]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnCompetitionType Context triple: [Fairs Cup Committee, basedOnCompetitionType, trade fairs cities concept]
-
A.
typeOfCompetition
Indicates the specific kind or category of competition in which an entity participates or is involved.
-
B.
appliesToCompetition
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable specifically to a competition.
-
C.
overseesCompetitionType
Indicates that one entity has responsibility for supervising, managing, or regulating a particular type or category of competition.
-
D.
coversCompetitionType
Indicates that one entity includes or addresses a particular type or category of competition.
-
E.
associatedCompetitionType
chosen
Indicates that one entity is linked to or involved with a particular type or category of competition.
- 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0059ca9048190b742e70e818ee64f |
completed | April 15, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:06 a.m.