Triple
T7649156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FC Prishtina |
E173200
|
entity |
| Predicate | success |
P127
|
FINISHED |
| Object | one of the most successful clubs in Kosovo |
—
|
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: one of the most successful clubs in Kosovo | Statement: [FC Prishtina, success, one of the most successful clubs in Kosovo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: success Context triple: [FC Prishtina, success, one of the most successful clubs in Kosovo]
-
A.
successMetric
Indicates the specific criterion or measure used to evaluate whether an action, process, or relationship has achieved its intended success.
-
B.
successRate
Indicates the proportion or frequency with which attempts at a given action or process result in a successful outcome.
-
C.
support
Indicates that one entity provides assistance, endorsement, or backing to another entity or its actions.
-
D.
status
chosen
Indicates the current condition, state, or standing of an entity within a given context.
-
E.
result
Indicates that one entity is produced, caused, or brought about as an outcome or consequence of another entity or process.
- 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_69c6995473348190a4f41d110d619a18 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7061cbc3c8190a917dd7e71214182 |
completed | March 27, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69c7015dd8fc8190bc5f52a12bd46209 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 3:58 p.m.