Triple
T6179269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KK Crvena zvezda |
E137897
|
entity |
| Predicate | regionOfLeague |
P14506
|
FINISHED |
| Object | Adriatic region |
—
|
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: Adriatic region | Statement: [KK Crvena zvezda, regionOfLeague, Adriatic region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionOfLeague Context triple: [KK Crvena zvezda, regionOfLeague, Adriatic region]
-
A.
regionLeague
chosen
Indicates a relationship where a specific region is associated with, belongs to, or is governed by a particular league or league-level organization.
-
B.
clubRegion
Indicates that a club is located in, associated with, or belongs to a particular geographic region.
-
C.
homeRegionLeague
Indicates that a league is the primary or native regional competition associated with an entity (such as a team or club).
-
D.
playsInConfederationRegion
Indicates that an entity (typically a sports team or club) competes within the geographic region governed by a specific confederation.
-
E.
participantsRegion
Indicates that the related entities are associated with, originate from, or operate within a specified geographic region.
- 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_69c008a80f748190ba3d07ffc81acb29 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05dcb77948190b5385438f81bf0a8 |
completed | March 22, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c055fa0a808190bda37832e3ac150c |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:18 p.m.