Triple
T35593462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turkish |
E1028562
|
entity |
| Predicate | hasRoundingHarmony |
P197682
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Turkish, hasRoundingHarmony, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoundingHarmony Context triple: [Turkish, hasRoundingHarmony, true]
-
A.
hasProperRounds
Indicates that an entity is associated with rounds that meet specified standards or criteria for being considered proper or valid.
-
B.
roundOf
Indicates that one event, match, or game occurs as a specific stage or phase within a larger competition or tournament.
-
C.
hasRound
Indicates that an entity possesses, includes, or is associated with a particular round (e.g., a round of an event, game, or process).
-
D.
hasHarmony
Indicates that two or more entities are in a state of balance, agreement, or pleasing coordination with one another.
-
E.
hasRoudNumber
Indicates that an entity is associated with or assigned a specific round number within a sequence of rounds or stages.
- F. None of above. chosen
Provenance (4 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
| PDg | Predicate description generation | batch_69fea1f4daa88190bd3cc1ace684e77f |
completed | May 9, 2026, 2:54 a.m. |
Created at: May 3, 2026, 4:05 p.m.