Triple
T37121874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FC Roskilde |
E919277
|
entity |
| Predicate | isInLeagueSystemOf |
P85906
|
FINISHED |
| Object | Denmark |
—
|
NE NERFINISHED |
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: Denmark | Statement: [FC Roskilde, isInLeagueSystemOf, Denmark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInLeagueSystemOf Context triple: [FC Roskilde, isInLeagueSystemOf, Denmark]
-
A.
isInSportSystemOf
chosen
Indicates that one entity belongs to, is organized within, or operates under the structure of a particular sport system or sports organizational framework of another entity.
-
B.
isPartOfLeague
Indicates that an entity belongs to, participates in, or is a member of a particular league.
-
C.
typeOfLeagueSystem
Indicates that one entity is the kind or structure of league system to which another entity belongs or in which it operates.
-
D.
usedInLeague
Indicates that an entity (such as a team, player, or item) participates or is employed within a particular league.
-
E.
representsInLeague
Indicates that an entity serves as a representative of another entity within a specific league or organized 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_69f76e9c57148190ba789dd059645bb9 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:15 p.m.