Triple
T456540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FC Dila Gori |
E7244
|
entity |
| Predicate | hasCompetitionType |
P2440
|
FINISHED |
| Object | domestic league |
—
|
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: domestic league | Statement: [FC Dila Gori, hasCompetitionType, domestic league]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompetitionType Context triple: [FC Dila Gori, hasCompetitionType, domestic league]
-
A.
hasCompetition
Indicates that one entity is in a state of rivalry or contest with another entity, typically competing for the same goal, resource, or advantage.
-
B.
typeOfCompetition
chosen
Indicates the specific kind or category of competition in which an entity participates or is involved.
-
C.
appliesToCompetition
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable specifically to a competition.
-
D.
hasWonCompetition
Indicates that an entity has achieved victory in a competition or contest against others.
-
E.
hasRelatedCompetition
Indicates that one competition is related to another competition in a meaningful way, such as being similar, connected, or associated within a shared context.
- 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efa1616481909399f92551a0c9e3 |
completed | Feb. 28, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69a2ede614b88190be07425f5535f56d |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.